Hot answers tagged

4

no. SSH/SFTP is not using SSL certificates, but SSH certificates or keys (unless you have specially crated SSH server and clients supporting this). But you can configure this way FTPs server for sharing your data. Or you can store the SSH fingerprints to SSHFP DNS records to avoid prompt on the side of users (also depends on the client software, if it ...


3

The client port number is independent of server running on port 12345. Usually the client when uses connect to any server, the system assigns a random port number for connection on its side. You need not worry about client side port numbers. They will have to configure their IP tables to be able to reach you. If any rule in IP tables on client side that ...


2

The problem is definitely not your key; it's most likely the server's Diffie-Hellman parameters -- or possibly their DSA key, but not too many people use DSA keys for SSH, especially since OpenSSH deprecated them recently. It might be worth taking a network trace to see exactly when the error is occurring: on initial negotiation of e.g. group14; or ...


2

Looking at your log file, apparently 3 key exchange algorithms are available: diffie-hellman-group-exchange-sha256, diffie-hellman-group14-sha1, diffie-hellman-group-exchange-sha1 With diffie-hellman-group-exchange-sha256 being the preferential one, as advertised by the server. The host has probably 2 keys: one RSA key and one ED25519 key. The ED25519 ...



Only top voted, non community-wiki answers of a minimum length are eligible