1. 4

I’m especially interested in experience using ssh for scripts

  1.  

  2. 3

    What makes you interested in Tectia over OpenSSH? I’d struggle to think of a reason not to use OpenSSH, considering it’s high-quality and well-supported.

    Speaking of other SSH implementations… remember ssh.com? And GNU lsh? (There’s also some things like Java implementations and curl’s, but those were the main competitors as I remember them.)

    1. 3

      ssh.com is tectia. https://www.ssh.com/products/tectia-ssh/

      I’m curious about experience with performance, security, and reliability. Openssh fails randomly for me at tolerable but annoying frequency.

      1. 2

        Can you give us some more detail on the problems you have with OpenSSH?

        I know that it’s not ideal for certain workloads (see, eg, the HPN patches), but if it’s failing that sounds like bug(s) that should be reported?

        1. 1

          I’m just a user of a ssh structured system that has intermittent failures that seem tied to ssh performance under load.

      2. 3

        I’d forgotten about lsh, but it still sees the odd bit of activity. Wikipedia has a tidy summary of available clients.

        Diversity is good, but I can’t see any reason to use anything other than OpenSSH (heck, Microsoft even has their own port).

        1. 2

          What makes you interested in Tectia over OpenSSH? I’d struggle to think of a reason not to use OpenSSH, considering it’s high-quality and well-supported.

          At the very least, avoiding a monoculture around a single implementation is probably a good security strategy.