In reverse connection -- NO.
If the key is omitted at server end, the listening viewer will still accept the connection without notification (still working under encryption, but not using the original pre-shared key.
Reference [topic=27039]Possible Bug ?? SecureVNC -- Client Authentication Keys[/topic] for more detail.
Thanks YY,
I'm talking about direct, client-initiated connection.
In this scenario, how can I configure the server to refuse the connection if the client doesn't provide the pre-shared key (instead of generate a new one on the fly)?
Not necessary to config the server to reject such a connection
For a server using SecureVNC with xxxx_Server_ClientAuth.pubkey,
a viewer without the corresponding xxxx_Viewer_ClientAuth.pkey is not able to establish a connection with that server. After input the password, an error message will be returned.