Remote Desktop / SSL / Authentication

i understand basics , ssl , basics of kerberos (the kerberos part i'll explain in moment).

when make remote desktop connection on internet, remote rdp gateway server, encrypt connection , give me warning certificate isn't trusted authority (didn't install certificate on end, or use well-known ca). (i think called self-signed?)

anyways, assume bad security model because of potential man-in-the-middle attacks, one.  could password (or password hash?)

my question is: there way setup rdp (or similar connections) functions more kerberos; in which, password (hash) encrypts connection attempt, , server can read because knows password (hash), making secret key password.

or doing , i'm confused?

to me, seems first establish connection using ssl cert, way before passes authentication information.

any ideas on this?

rdp ssl security enabled default self-signed certificate on windows server 2008 , above , why receive certificate validation error. rdp ssl works same way http ssl does, means connection encrypted , authenticated if server certificate can verified. in other words, certificate error may indicate man-in-the-middle situation unless certificate known not trusted.

there 2 types of authentication available in rdp today, rdp uses network level authentication if possible/enabled/supported otherwise uses standard rdp authentication occurs within rdp session. in both cases authentication data protected using encryption, more details encryption , protection levels please check technet article:

http://technet.microsoft.com/en-us/library/cc782610(ws.10).aspx

http://technet.microsoft.com/en-us/library/cc732713.aspx

/hasain

Windows Server  >  Security