search for: sshkey_equ

...he "host key found matching a different > name/address" is triggered when a key received from the server in an update > already exists under a different name. If you turn the debugging level up, > then you'll see the name(s) that it matches too: > > 2100 if (sshkey_equal(l->key, ctx->keys[i])) { > 2101 ctx->other_name_seen = 1; > 2102 debug3_f("found %s key under different " > 2103 "name/addr at %s:%ld", > 2104 sshkey_ssh_name(ctx->keys[...

...+#ifdef WITH_OPENSSL /* XXX ed25519_1_pw is encrypted with aes256-cbc */ TEST_START("parse Ed25519 from private w/ passphrase"); buf = load_file("ed25519_1_pw"); ASSERT_INT_EQ(sshkey_parse_private_fileblob(buf, @@ -408,6 +413,7 @@ sshkey_file_tests(void) ASSERT_INT_EQ(sshkey_equal(k1, k2), 1); sshkey_free(k2); TEST_DONE(); +#endif TEST_START("load Ed25519 from public"); ASSERT_INT_EQ(sshkey_load_public(test_data_file("ed25519_1.pub"), &k2, diff --git a/regress/unittests/sshkey/test_fuzz.c b/regress/unittests/sshkey/test_fuzz.c index 1f08a2...

...nswer to your question. The "host key found matching a different name/address" is triggered when a key received from the server in an update already exists under a different name. If you turn the debugging level up, then you'll see the name(s) that it matches too: 2100 if (sshkey_equal(l->key, ctx->keys[i])) { 2101 ctx->other_name_seen = 1; 2102 debug3_f("found %s key under different " 2103 "name/addr at %s:%ld", 2104 sshkey_ssh_name(ctx->keys[i]), 2105...

Hi, I created new host keys on serverA, updated sshd_config accordingly (adding the line below) and restarted ssh: cd /etc/ssh sudo ssh-keygen -f 2024_ssh_host_ed25519_key -t ed25519 -N '' sudo vi /etc/ssh/sshd_config # added line: HostKey /etc/ssh/2024_ssh_host_ed25519_key sudo service ssh restart When I connect to serverA (`ssh -v -o UpdateHostKeys=yes serverA`) afterwards,

...ven public key */ +/* return matching Identity for given public key */ static Identity * lookup_identity(struct sshkey *key, int version) { @@ -205,7 +238,22 @@ lookup_identity(struct sshkey *key, int Idtab *tab = idtab_lookup(version); TAILQ_FOREACH(id, &tab->idlist, next) { - if (sshkey_equal(key, id->key)) + if (sshkey_equal(key, id->idkey->key)) + return (id); + } + return (NULL); +} + +/* return matching private key for given public key */ +static Identity * +lookup_identity_unshadowed_key(struct sshkey *key, int version) +{ + Identity *id; + + Idtab *tab = idtab_lookup...

...matching a different > > name/address" is triggered when a key received from the server in an update > > already exists under a different name. If you turn the debugging level up, > > then you'll see the name(s) that it matches too: > > > > 2100 if (sshkey_equal(l->key, ctx->keys[i])) { > > 2101 ctx->other_name_seen = 1; > > 2102 debug3_f("found %s key under different " > > 2103 "name/addr at %s:%ld", > > 2104 sshkey_ss...

...nect2.c > +++ b/sshconnect2.c > @@ -1243,6 +1243,14 @@ load_identity_file(Identity *id) > quit = 1; > break; > } > + if (private != NULL && id->key != NULL && > + !sshkey_equal(id->key, private)) { > + error("Load key \"%s\": private key does not match " > + "public key", id->filename); > + sshkey_free(private); > + private = NULL;...

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

Hi, OpenSSH 6.9 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This release contains some substantial new features and a number of bugfixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is

Hi, The main (and probably the only) use case of this PAM module is to let sudo authenticate users via their ssh-agent, therefore without having to type any password and without being tempted to use the NOPASSWD sudo option for such convenience. The principle is originally implemented by an existing module [0][1] and many pages that explain how to use it for such purpose can be found online.