morgan/UxPlay
1
0
Fork 0
mirror of https://github.com/morgan9e/UxPlay synced 2026-04-14 00:04:13 +09:00
Code Issues Packages Projects Releases Wiki Activity

README updates

Browse Source
This commit is contained in:
F. Duncanh
2023-12-26 15:03:15 -05:00
parent e63be544a5
commit 48f810c344
3 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
README.html
View File

@@ -465,17 +465,17 @@ clients to “pair” with the UxPlay server the first time they connect to
it, by entering a 4-digit pin code that is displayed on the UxPlay
terminal. (This is optional, but sometimes required if the client is a
corporately-owned and -managed device with MDM Mobile Device
Management.) Pairing occurs just once, is currently only recorded in the
client, and persists unless the UxPlay public key is changed. By default
(since v1.68) the public key is now generated using the “Device ID”,
which is either the server’s hardware MAC address, or can be set with
the -m option (most conveniently using the startup option file).
(Storage of a more securely-generated persistent key as an OpenSSL “pem”
file is still available with the -key option). For use of uxplay in a
more public environment, a list of previously-registered clients can
(since v1.68) be optionally-maintained using the -reg option: without
this option, returning clients claiming to be registered are just
trusted and not checked.</p></li>
Management.) Pairing occurs just once, is currently only recorded by the
client unless the -reg option is used, and persists until the UxPlay
public key is changed. By default (since v1.68) the public key is now
generated using the “Device ID”, which is either the server’s hardware
MAC address, or can be set with the -m option (most conveniently using
the startup option file). (Storage of a more securely-generated
persistent key as an OpenSSL “pem” file is still available with the -key
option). For use of uxplay in a more public environment, a list of
previously-registered clients can (since v1.68) be optionally-maintained
using the -reg option: without this option, returning clients claiming
to be registered are just trusted and not checked.</p></li>
<li><p>By default, UxPlay is locked to its current client until that
client drops the connection; since UxPlay-1.58, the option
<code>-nohold</code> modifies this behavior so that when a new client

2
README.md
View File

@@ -379,7 +379,7 @@ help with this or other problems.
the first time they connect to it, by entering
a 4-digit pin code that is displayed on the UxPlay terminal. (This is optional, but sometimes required if the client is a
corporately-owned and -managed device with MDM Mobile Device Management.) Pairing occurs just once, is currently only
recorded in the client, and persists unless the
recorded by the client unless the -reg option is used, and persists until the
UxPlay public key is changed. By default (since v1.68) the public key is now generated using the "Device ID", which is either the server's
hardware MAC address, or
can be set with the -m option (most conveniently using the startup option file). (Storage of a more securely-generated

24
README.txt
View File

@@ -455,18 +455,18 @@ below for help with this or other problems.
entering a 4-digit pin code that is displayed on the UxPlay
terminal. (This is optional, but sometimes required if the client is
a corporately-owned and -managed device with MDM Mobile Device
Management.) Pairing occurs just once, is currently only recorded in
the client, and persists unless the UxPlay public key is changed. By
default (since v1.68) the public key is now generated using the
"Device ID", which is either the server's hardware MAC address, or
can be set with the -m option (most conveniently using the startup
option file). (Storage of a more securely-generated persistent key
as an OpenSSL "pem" file is still available with the -key option).
For use of uxplay in a more public environment, a list of
previously-registered clients can (since v1.68) be
optionally-maintained using the -reg option: without this option,
returning clients claiming to be registered are just trusted and not
checked.
Management.) Pairing occurs just once, is currently only recorded by
the client unless the -reg option is used, and persists until the
UxPlay public key is changed. By default (since v1.68) the public
key is now generated using the "Device ID", which is either the
server's hardware MAC address, or can be set with the -m option
(most conveniently using the startup option file). (Storage of a
more securely-generated persistent key as an OpenSSL "pem" file is
still available with the -key option). For use of uxplay in a more
public environment, a list of previously-registered clients can
(since v1.68) be optionally-maintained using the -reg option:
without this option, returning clients claiming to be registered are
just trusted and not checked.
- By default, UxPlay is locked to its current client until that client
drops the connection; since UxPlay-1.58, the option `-nohold`