mirror of
https://github.com/morgan9e/UxPlay
synced 2026-04-14 16:24:29 +09:00
README update to document -pw changes
This commit is contained in:
25
README.txt
25
README.txt
@@ -1083,15 +1083,22 @@ deregisters the corresponding client (see options -restrict, -block,
|
||||
the startup file if you wish to use this feature.)*
|
||||
|
||||
**-pw** \[*pwd*\]. (since 1.72). As an alternative to -pin, client
|
||||
access can be controlled with a password set when uxplay starts (set it
|
||||
in the .uxplay startup file, where it is stored as cleartext.) All users
|
||||
must then know this password. This uses HTTP md5 Digest authentication,
|
||||
which is now regarded as providing weak security, but it is only used to
|
||||
validate the uxplay password, and no user credentials are exposed. If
|
||||
*pwd* is **not** specified, a random 4-digit pin code is displayed, and
|
||||
must be entered on the client at **each** new connection. *Note: -pin
|
||||
and -pw are alternatives: if both are specified at startup, the earlier
|
||||
of these two options is discarded.*
|
||||
access can be controlled with a password. If a password *pwd* (of length
|
||||
at least six characters) is set when uxplay starts (usually set in the
|
||||
startup file, where it is stored as cleartext), all users must know this
|
||||
password to connect to UxPlay (the client prompts for it). This method
|
||||
uses HTTP md5 Digest authentication, which is now regarded as providing
|
||||
weak security, but it is only used to validate the uxplay password, and
|
||||
no user credentials are exposed. After a successful authentication, the
|
||||
client stores the password, and will use it initially for future
|
||||
authentications without prompting, so long as the UxPlay deviceID has
|
||||
not changed (this initial authentication will fail if the UxPlay
|
||||
password has changed). If *pwd* is **not** specified with the -pw option
|
||||
when UxPlay starts, a new random 4-digit pin code is generated and
|
||||
displayed on the UxPlay terminal for **each** new connection, and must
|
||||
be entered on the client (there are three chances to enter it, before it
|
||||
is changed). *Note: -pin and -pw are alternatives: if both are specified
|
||||
at startup, the earlier of these two options is discarded.*
|
||||
|
||||
**-vsync \[x\]** (In Mirror mode:) this option (**now the default**)
|
||||
uses timestamps to synchronize audio with video on the server, with an
|
||||
|
||||
Reference in New Issue
Block a user