Talk:Comparison of SSH servers

Latest comment: 1 year ago by PK650 in topic Request to clarify table data for wolfSSH

New addition to the comparison

edit

Add TinySSHd?

Trimming in OS compatibility table

edit

I've deleted both Palm OS and Windows Mobile, as none of the SSH servers in de comparison table supported either OS. No point of having them in there if al the answers are No anyway. — Preceding unsigned comment added by 82.72.18.227 (talk) 19:57, 20 September 2012 (UTC)Reply

Maybe de-list freeFTPd

edit

I installed the software on Windows-7 and nothing worked. The UI was buggy and hung. I then went to "Programs and Features" to uninstall, but it reported that it was not able to completely remove it. Now I have garbage in the registry and corrupt entries in the services control panel. I recommend NOT installing this buggy software! — Preceding unsigned comment added by 76.116.87.151 (talk) 00:11, 31 March 2013 (UTC)Reply

Agent Forwarding

edit

Please add "Agent Fowarding" to the table. Not all servers seams to support this - would be interesting to know. — Preceding unsigned comment added by 2A00:E50:F155:B:5176:ADF:6B5:C69A (talk) 13:01, 30 September 2015 (UTC)Reply

Certificates

edit

I think it would be interesting with a comparison of certificate support. OpenSSH has their own certificate/CA implementation which is simpler than X.509. I think I've heard of SSH implementations that support X.509. — Preceding unsigned comment added by 89.102.141.20 (talk) 18:06, 5 November 2015 (UTC)Reply

Add VShell?

edit

I am not sure the proper way to suggest this, since I work for Vandyke Software, and I could use some assistance. VShell Server is missing from this list. It seems like it should be included. VShell Server was first released 2000-12-12, with the latest release date on 2017-10-24. I'd be happy to provide information for the platform and feature tables. I've collected external references, including:

SSH, the Secure Shell: The Definitive Guide, O'Reilly & Associates (2001). Dept. of Computer Science, Univ. of Virginia. [1]

Lewis, Shawn. “A Discussion of SSH Secure Shell.” SANS Institute InfoSec Reading Room, 2001. [2].

Dwivdei, Himanshu. “Implementing SSH: Strategies for Optimizing the Secure Shell.” Wiley Publishing Inc. 2004, p. 141. [3]

Messmer, Ellen. “Companies mull commercial vs. freeware SSH.”, Network World. Jan 5, 2004. [4]

Heller, Alex D. “Global Information Assurance Certification Paper. Secure Options for File Transfer.” Version 1.3 April 06, 2002. Page 10. [5]

Miller, David R. and Gregg, Michael. “Security Administrator Street Smarts: A Real World Guide to CompTIA Security and Skills.” Wiley Publishing Inc. 2011, p. 397. [6]

Weiss, Aaron. “VShell Puts a Friendly Face on Secure Transfers.” Enterpise Networking Planet, Oct 16, 2006. [7] — Preceding unsigned comment added by Jilliancnm (talkcontribs) 22:32, 29 November 2017 (UTC)Reply

SecureCRT Wikipedia page [8]

VanDyke Software's VShell Server web page: [9]

Would someone be willing to review VShell for inclusion and/or discuss the addition of VShell?

Jilliancnm (talk) 23:00, 16 November 2017 (UTC)Reply

References

  Declined As far as I know, SecureCRT is the successor to VShell. But if VShell still is used today, the first step would be the creation of a VShell Wikipedia page, which needs to exist before the technology can be added to this list.  Spintendo  ᔦᔭ  00:43, 12 December 2017 (UTC)Reply
To clarify, SecureCRT is not the successor to VShell. SecureCRT is an SSH-based client application. VShell is a separate, SSH server that is in active development and has been since December 12, 2000. Thank you for the response and the suggestion to create a VShell Wikipedia page. Jilliancnm (talk) 17:44, 13 December 2017 (UTC)Reply

Request to clarify table data for wolfSSH

edit
  • Specific text to be added or removed:
    • Update Platform table, wolfSSH row, webOS column entry, to clarify NO support
  • Reason for the change:
    • The existing entry for wolfSSH's webOS support has an unknown (??) status. This request is to clarify the entry to have an accurate representation of the state of the wolfSSH product.
  • References supporting change:

Tim-Weller-wolfSSL (talk) 19:59, 15 December 2022 (UTC)Reply

  Done PK650 (talk) 07:13, 8 January 2023 (UTC)Reply