Nick you would be correct, it does not support NLA, since Microsoft is
retiring that protocol its best not to use it anyways.
TLS with a certificate will be secure. or you can install openssl
3.0.8.x enable FIPS140-2 will work for compliance requirements.
*Thank You*
Sean Hulbert
*Security Centric Inc.*
A Cybersecurity Virtualization Enablement Company
/StormCloud Gov, Protected CUI Environment!/
Industry's most secure CMMC virtual desktops!
*/FedRAMP MIL4 in process (RAR)/*
System Award Management
*CAGE: 8AUV4*
*SAM ID: UMJLJ8A7BMT3*
AFCEA San Francisco Chapter President
If you have heard of a hacker by name, he/she has failed, fear the
hacker you haven’t heard of!
CONFIDENTIALITY NOTICE: This communication with its contents may contain
confidential and/or legally privileged information. It is solely for the
use of the intended recipient(s). Unauthorized interception, review, use
or disclosure is prohibited and may violate applicable laws including
the Electronic Communications Privacy Act. If you are not the intended
recipient, please contact the sender and destroy all copies of the
communication. Content within this email communication is not legally
binding as a contract and no promises are guaranteed unless in a formal
contract outside this email communication.
igitur qui desiderat pacem, praeparet bellum!!!
Epitoma Rei Militaris
On 6/21/2024 12:32 PM, Nick Couchman wrote:
On Wed, Jun 19, 2024 at 5:10 AM Dark Corner <darkcorner...@gmail.com>
wrote:
It doesn't connect with RealVNC.
The original Viewers and Servers need the account on realvnc.com
<http://realvnc.com>, then a second password must be set on the
server for the connection.
Yeah, I did a little digging on this, and it looks like RealVNC has
pretty well made their solution a proprietary one - even if you start
a RealVNC server with -Authentcation=None, the negotiation between
client and server shows that the server supports several security
types - 13, 133, 5, and 129, IIRC - none of which libvncclient support
([1]). I don't know if other VNC clients, like (Tight, Tiger, Ultra)
are capable of connecting to RealVNC, but I'd be a bit surprised -
RealVNC seems to be taking their product in the direction of
TeamViewer, AnyDesk, NoMachine, etc., where they want you to subscribe
to and broker through their cloud service, and aren't interested in
actually providing a RFB-compatible server.
I tried both the Xubuntu user credentials and the RVNC username
plus the connection password.
It does not work.
I could install another VNC, but I can't remove the RVNC because
it is already needed by a technician.
You might still be able to install another VNC server and use a
different port number. But, hard to say how well (or poorly) multiple
VNC servers will cooperate together.
I installed xrdp following the reported guide.
I then cloned an RDP connection to a Win10 PC already tested as
working.
I then changed the IP Address and using the credentials of a
Xubuntu user, but when I try to connect I am immediately disconnected.
The "Security mode" option must always be on NLA (Network Level
Authentication)?
I do not believe that xrdp supports NLA - I think you need TLS.
Should "Ignore server certificate" be On or Off?
For testing, you can turn it on so that the certificate validity isn't
an issue - in Real Life, you should make sure you trust your server
certificates.
-Nick
