Re: traffic encryption

From: Bodo Eggert (
Date: 08/05/05

  • Next message: Volker Birk: "Re: traffic encryption"
    Date: Fri, 05 Aug 2005 14:28:39 +0200

    Roman Mashak <> wrote:

    > here it asks password. Sure, we can avoid it using 'ssh-keygen -t rsa' and
    > etc. but it's still some burden, due to fact we should manage these keys
    > among thousands of clients (in my case).

    What about stunnel?

    Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
    verbreiteten Lügen zu sabotieren.

  • Next message: Volker Birk: "Re: traffic encryption"

    Relevant Pages

    • Re: traffic encryption
      ... ??>> these keys among thousands of clients. ... With best regards, Roman Mashak. ...
    • Re: [Full-Disclosure] SSH vs. TLS
      ... > frowned upon by network ops and security. ... > - There must be a secure means by which all server keys are distributed to ... > appropriate ssh clients. ... > servers from using expired keys. ...
    • Re: Its time for those 2048-, 3072-, and 4096-bit keys?
      ... > basically) can't handle keys over 1024 bits in length, ... > which may have old clients connection. ... > "Niklaus Wirth has lamented that, whereas Europeans pronounce his name ... Americans invariably mangle it into ...
    • Re: Need to revert behavior of OpenSSH to the old key order ...
      ... Everything goes just fine, but when I am done, existing clients are now presented with this message: ... The authenticity of host 'hostname ' can't be established ... You must be using different keys for your server than the one that has ... If I simply REMOVE the RSA keys, the error goes away, and existing DSA-using clients no longer bomb out, but this is NOT a good solution for two reasons: ...
    • Re: Blocked remote calls with COM+ and MSDTC
      ... appears to have been lost! ... _keys table you get interleaved rows. ... For instance say two clients cause ... assume they have been given the ID of the start of a contiguous range of IDs they ...