This isn't a web forum where you could "bump" posts.
I apologize.
Maybe you could instead explain why you believe you need to make your users ignore that warning?
The DNS name is a VIP. There is a load balancer that connects the user to one of many servers. When the load balancer connects the users to a new backend server, they see the "scary" SSH warning. I understand your concern with initially disabling host checking under normal conditions, but this environment is highly controlled and the network is isolated. I also would only disable host key checking for this specific domain.
Thank you, Ivan G.
On Mar 26, 2017, at 1:31 PM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
Am 26.03.2017 um 19:24 schrieb Ulrich Sibiller:
If you have a DHCP environment without decent hostkey management disabling struct hostkey checks makes it a bit more comfortable.
His screenshot clearly shows him using a DNS name (x2go.ace.analysisgroup.com), so the underlying IP should not matter, even if it changes dynamically ...
Please do not judge the user's desire as inappropriate without knowing his reasons...
Which is why I asked him to take a few steps backward and explain the actual problem he is trying to solve.
-Stefan
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user