Displaying 20 results from an estimated 3000 matches similar to: "nistp256 preferred over ed25519"
2020 Sep 16
2
ssh-ed25519 and ecdsa-sha2-nistp256 host keys
Here you go:
OpenSSH_7.9p1, OpenSSL 1.1.1d 10 Sep 2019
debug1: Reading configuration data /home/ryantm/.ssh/config
debug1: /home/ryantm/.ssh/config line 4: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 13: Applying options for *
debug2: resolving "{REDACTED}" port 22
debug2: ssh_connect_direct
debug1: Connecting to
2018 Nov 23
2
Debian Stretch 9.6: openssh-server and old dropbear client don't work togheter
Il giorno gio 22 nov 2018 alle ore 21:24 Stuart Henderson
<stu at spacehopper.org> ha scritto:
>
> On 2018/11/22 19:55, owl700 at gmail.com wrote:
> > Hi, I have compatibility issues with the latest version of
> > openssh-server and an old dropbear client, the dopbear client stops at
> > preauth
> >
> > ov 22 14:34:03 myhostname sshd[3905]: debug1: Client
2025 Jan 20
3
[Bug 3779] New: SHA1 deprecation
https://bugzilla.mindrot.org/show_bug.cgi?id=3779
Bug ID: 3779
Summary: SHA1 deprecation
Product: Portable OpenSSH
Version: 8.4p1
Hardware: Other
OS: Linux
Status: NEW
Severity: trivial
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
Reporter:
2025 May 13
5
[Bug 3823] New: SSH on same device ignores MAC restrictions
https://bugzilla.mindrot.org/show_bug.cgi?id=3823
Bug ID: 3823
Summary: SSH on same device ignores MAC restrictions
Product: Portable OpenSSH
Version: 10.0p2
Hardware: Other
OS: Other
Status: NEW
Severity: major
Priority: P5
Component: ssh
Assignee: unassigned-bugs at
2024 May 16
2
[Bug 3691] New: Connection to localhost succeeds with disabled MAC
https://bugzilla.mindrot.org/show_bug.cgi?id=3691
Bug ID: 3691
Summary: Connection to localhost succeeds with disabled MAC
Product: Portable OpenSSH
Version: 9.7p1
Hardware: amd64
OS: Other
Status: NEW
Severity: normal
Priority: P5
Component: sshd
Assignee: unassigned-bugs at
2025 Apr 17
2
[Bug 3814] New: incorrect signature when ssh'ing to an AIX server (Big Endian) from amd64 (Little endian)
https://bugzilla.mindrot.org/show_bug.cgi?id=3814
Bug ID: 3814
Summary: incorrect signature when ssh'ing to an AIX server (Big
Endian) from amd64 (Little endian)
Product: Portable OpenSSH
Version: 10.0p1
Hardware: PPC64
OS: AIX
Status: NEW
Severity: major
Priority: P5
2020 Mar 02
3
Question about host key algorithms
When I do ssh -Q key, where ssh is the OpenSSH 7.4p1 client, I get the
following output:
ssh-ed25519
ssh-ed25519-cert-v01 at openssh.com
ssh-rsa
ssh-dss
ecdsa-sha2-nistp256
ecdsa-sha2-nistp384
ecdsa-sha2-nistp521
ssh-rsa-cert-v01 at openssh.com
ssh-dss-cert-v01 at openssh.com
ecdsa-sha2-nistp256-cert-v01 at openssh.com
ecdsa-sha2-nistp384-cert-v01 at openssh.com
ecdsa-sha2-nistp521-cert-v01 at
2016 Oct 24
1
SSH fail to login due to hang over after authenticated.
Can you confirm if the problem is specific to the ssh client, or the ssh
server? (Try to ssh into the same server from different client, and to some
different server from the same client)
On Mon, Oct 24, 2016 at 9:41 PM, Jin Li <lijin.abc at gmail.com> wrote:
> Hi OpenSSH,
>
> I encountered that SSH will hang over after I input the password.
> Could you help show me how to
2013 Nov 12
0
OpenSSH 6.4 connection to Cisco 6506 routers/switches fails
Just upgraded to OpenSSH_6.4 with OpenSSL 1.0.1e and libz.so.1.2.8.
Now some (but not all) Cisco router logins hang:
kraken> ssh -vv -l noc XXX-mgmt.gw
OpenSSH_6.4, OpenSSL 1.0.1e 11 Feb 2013
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 50: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to XXX-mgmt.gw [10.12.0.1] port 22.
2020 Mar 02
4
Question about host key algorithms
$ ssh -Q HostKeyAlgorithms
Unsupported query "HostKeyAlgorithms"
$ ssh -V
OpenSSH_7.4p1, OpenSSL 1.0.2u 20 Dec 2019
On Mon, Mar 2, 2020 at 2:24 PM Christian Hesse <list at eworm.de> wrote:
> Luveh Keraph <1.41421 at gmail.com> on Mon, 2020/03/02 14:07:
> > When I do ssh -Q key, where ssh is the OpenSSH 7.4p1 client, I get the
> > following output:
> >
2016 Apr 19
4
Client-side public key causing mess
Hello,
I have a client machine and a server machine. I generated a pair of
private-public rsa keys using ssh-keygen.
On the client-machine, I uploaded my private key onto ~/.ssh/id_rsa
On the server machine, I appended the content of the public key to
.ssh/authorized_keys
I can successfully connect from the client to the server with that config.
However, on the client-side, if I add a
2020 Oct 07
0
dbus issue on centos 7 as a lxc container
Hi,
dbus on centos 7 lxc won't work.
So I'm unable to start or query status units with systemd, for example:
systemctl status
Failed to get D-Bus connection: No such file or directory
I have no issues with centos 8 container (debian 10 ones work fine too)
This is the output of ps aux on centos 7:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root
2018 May 25
5
Strange crypto choices
The defaults for HostKeyAlgorithms option are:
ecdsa-sha2-nistp256-cert-v01 at openssh.com,
ecdsa-sha2-nistp384-cert-v01 at openssh.com,
ecdsa-sha2-nistp521-cert-v01 at openssh.com,
ssh-ed25519-cert-v01 at openssh.com,
ssh-rsa-cert-v01 at openssh.com,
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
ssh-ed25519,ssh-rsa
Why does OpenSSH prefer older and less secure
2019 Oct 17
0
DSA key not accepted on CentOS even after enabling
PubkeyAcceptedKeyTypes=+ssh-dss
You also need that ^^ in their client if they are running on el8 machine
as well .. i needed to put it in my ~/.ssh/config when connecting FROM
an el8 machine to somewhere else.
On 10/17/19 9:27 AM, Gianluca Cecchi wrote:
> Hello,
> I have some users that connect to a server with their DSA key that is of
> type ssh-dss.
> I'm migrating (installing
2016 Oct 24
2
SSH fail to login due to hang over after authenticated.
Hi OpenSSH,
I encountered that SSH will hang over after I input the password.
Could you help show me how to resolve this problem? Thanks for your
help.
Please find the ssh debug info and my ssh version as below.
$ ssh -vvv user1 at remote_host
OpenSSH_6.9p1, LibreSSL 2.1.8
debug1: Reading configuration data /Users/user1/.ssh/config
debug1: /Users/user1/.ssh/config line 36: Applying options for
2016 Feb 09
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity
Thread split from my previous communication. Here is the integrity logs on
the platform. I had to cut this should due to the length of the logs (5Mb).
***************** failed-regress.log ************
trace: test integrity: hmac-sha1 @2900
FAIL: unexpected error mac hmac-sha1 at 2900: Bytes per second: sent
65665.7, received 55994.0.
trace: test integrity: hmac-sha1 @2901
FAIL:
2011 May 18
1
Problem SSHing to HP ILO SSH-2.0-mpSSH_0.1.0 with 5.8p1
Hi everyone,
We are recently seeing a problem with OpenSSH 5.8p1 and SSH to ILO cards
running SSH-2.0-mpSSH_0.1.0.
This has previously worked with OpenSSH 5.5p1 (last known version for us
to work).
ssh ilohost -vvv gives the following on 5.8p1:
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Applying options for *.*
debug2: ssh_connect: needpriv 0
2019 Oct 17
2
DSA key not accepted on CentOS even after enabling
Hello,
I have some users that connect to a server with their DSA key that is of
type ssh-dss.
I'm migrating (installing as new) the server where they connect to CentOS 8
+ updates.
I was not able to connect with the keys to this new server even after
having added, as found in several internet pages, this directive at the end
of /etc/ssh/sshd_config of the CentOS 8 server:
# Accept also DSA
2018 Mar 06
2
Failed connections 7.6 to 5.2
Trying to connect to a Dell iDRAC 6. The iDRAC reports it is running
OpenSSH 5.2.
From Fedora Linux 20 with OpenSSH 6.4p1, connections succeed.
From Fedora Linux 23 with OpenSSH 7.2p2, connections succeed.
From Fedora Linux 27 with OpenSSH 7.6p1, connections fail prior to
prompting for a password. The message is, "Received disconnect from (IP
address) port 22:11: Logged out." Trying
2016 Feb 09
2
Test Failure OpenSSH 7.1 P2 on HPE NSE for key-commands
Thread split from my previous communication. Here is the key-commands logs
on the platform.
***************** failed-regress.log ************
trace: AuthorizedKeysCommand with arguments
FAIL: connect failed
trace: AuthorizedKeysCommand without arguments
FAIL: connect failed
***************** failed-ssh.log ************
trace: AuthorizedKeysCommand with arguments