On 01/31/2017 12:23 AM, FORT David wrote: > Le 31/01/2017 à 06:18, ToddAndMargo a écrit : >> Hi All, >> >> $ rpm -qa \freerdp\* >> freerdp-plugins-1.0.2-10.el7.x86_64 >> freerdp-libs-1.0.2-10.el7.x86_64 >> freerdp-1.0.2-10.el7.x86_64 >> >> I am trying to see if I can use xfreerdp in place of my currently working >> rdesktop. I am unable to connect to any of the rdp servers (Windows >> 7 Pro) that I can with rdesktop. >> >> Questions: >> 1) it prompts me for a password. Whose password? Mine, >> there's, a certificate's password? If it is a certificates >> password >> how the &*$@ am I suppose to know that? >> >> 2) What is all this garbage that comes up? >> >> I am confused, >> -T >> >> >> $ xfreerdp -t xxxx -u yyyy www.xxx.yyy.zzz >> connected to www.xxx.yyy.zz:xxxx >> The host key for www.xxx.yyy.zzz has changed >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ >> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ >> IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! >> Someone could be eavesdropping on you right now (man-in-the-middle attack)! >> It is also possible that a host key has just been changed. >> The fingerprint for the host key sent by the remote host is >> <<redacted>> >> Please contact your system administrator. >> Add correct host key in ~/.freerdp/known_hosts to get rid of this message. >> Host key for www.xxx.yyy.zzz has changed and you have requested strict >> checking. >> Host key verification failed. >> tls_connect: certificate not trusted, aborting. >> > It's the password associated with your yyyy account,
Why in the world does it ask for a password when no account is specified ?? > as xfreerdp tries > to do some NLA by default (and so the password can't be given on the > graphical login screen). > > Try with /sec:tls or /sec:rdp to use the corresponding security mode. > Cleaning up your ~/.freerdp/known_hosts file could help too. > > Best regards. > Well, it is a little better with /sec:tls or /sec:rdp, but ... $ /opt/freerdp-nightly/bin/xfreerdp /t:aaaa /u:yyyy /sec:rdp /v:ccc.ddd.eee.fff [00:49:50:243] [1425:1426] [ERROR][com.freerdp.core] - failed to connect to ccc.ddd.eee.fff [00:49:50:243] [1425:1426] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure [00:49:50:243] [1425:1426] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [00:49:50:243] [1425:1426] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure [00:49:50:243] [1425:1426] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1 $ /opt/freerdp-nightly/bin/xfreerdp /t:aaaa /u:yyyy /sec:tls /v:ccc.ddd.eee.fff [00:50:26:771] [1447:1448] [ERROR][com.freerdp.core] - failed to connect to ccc.ddd.eee.fff [00:50:26:771] [1447:1448] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure [00:50:26:771] [1447:1448] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C] [00:50:26:771] [1447:1448] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure [00:50:26:771] [1447:1448] [ERROR][com.freerdp.client.x11] - Freerdp connect error exit status 1 -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel