I agree with this. One of the things Snoden revealed was that the NSA
hung on to a large number of compromised keys to tain access to encrypted data.
In light of that re-using the same key is just making things too easy.-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Fri, 6 Oct 2017, Mihai Moldovan wrote:
Date: Fri, 6 Oct 2017 03:12:57 +0200 From: Mihai Moldovan <io...@ionic.de> To: Max A. <lith...@mail.ru>, x2go-user@lists.x2go.org Subject: Re: [X2Go-User] ssh-keygen.exe loads the processor every time the client starts On 09/28/2017 01:49 PM, Max A. wrote:I'm using a x2go server on CentOS 6.9 (the latest version from EPEL, 4.0.1.20), clients use Windows XP/7 and the latest version of X2Go Client (4.1.0.0-2017.03.11). Each time the client connects, ssh-keygen.exe (C:\Program Files\x2goclient\ssh-keygen.exe) starts with the parameters "-t rsa -b 4096 -N" "-C" X2Go Client RSA user key "-f C: /Users/max/.x2go/ssh/gen/key.fl1416 ". On not very powerful computers, this causes a delay of a few seconds with each connection and irritates users. Tell me please, if it is possible to generate this key once and for all?I understand that this may be inconvenient, but no, there's currently no way to generate a set of keys that will be re-used. I explicitly decided against that. For more information and the rationale for this change, refer to the release announcement: http://lists.x2go.org/pipermail/x2go-announcements/2017/000302.html Mihai
_______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
