search for: keytype

...ne: KEX2. debug: userauth-request for user jphillips service ssh-connection method none debug: Starting up PAM with username "jphillips" Failed none for jphillips from 209.186.189.140 port 63337 ssh2 debug: userauth-request for user jphillips service ssh-connection method publickey debug: keytype ssh-dss debug: test key... debug: keytype ssh-dss debug: keytype ssh-dss debug: matching key found: file /home/jphillips/.ssh/authorized_keys2, line 2 debug: PAM setting rhost to "linux2.matrasystems.com" Postponed publickey for jphillips from 209.186.189.140 port 63337 ssh2 debug: userau...

Hello Im just been working with puppet, the first usecase i have is to set up a system to create users and then push ssh keys on this machines in the create users .ssh files. I just started with puppet so i am a bit cluesless, Can someone push me in the right direction? Im having a centos enviorment. -- You received this message because you are subscribed to the Google Groups "Puppet

Anthony Scarpino wrote (elsewhere): > While writing up the man page.. I thought of a few things that I was > wondering if you considered.. > > Can an encrypted dataset (keytype=dataset) reside in a non-encrypted (no > kek defined) pool? I can see a case for and against allowing this when considering it purely at the feature level as users/admins see things. The admin can control wither users can enable encryption or not by delegating (or not) the "encryption&...

Anthony Scarpino wrote (elsewhere): > While writing up the man page.. I thought of a few things that I was > wondering if you considered.. > > Can an encrypted dataset (keytype=dataset) reside in a non-encrypted (no > kek defined) pool? I can see a case for and against allowing this when considering it purely at the feature level as users/admins see things. The admin can control wither users can enable encryption or not by delegating (or not) the "encryption&...

...: needpriv 0 debug1: Connecting to sam [127.0.0.1] port 22. debug1: Connection established. debug1: identity file /home/rmarshall/.ssh/identity type 0 debug3: Not a RSA1 key file /home/rmarshall/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace deb...

...rt SSH_AUTH_SOCK; SSH_AGENT_PID=2283; export SSH_AGENT_PID; echo Agent pid 2283; The interesting bits from an 'ssh -vvv localhost' session are: ... debug3: Not a RSA1 key file /Users/jd/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace ... debug3: key_read: missing whitespace debug2: key_type_from_...

...39;DOMAIN.ORGhostclient.domain.org' default_iteration_count : 0x00001000 (4096) num_keys : 0x0004 (4) keys: ARRAY(4) keys: struct secrets_domain_info1_kerberos_key keytype : 0x00000012 (18) iteration_count : 0x00001000 (4096) value : DATA_BLOB length=32 keys: struct secrets_domain_info1_kerberos_key keytype : 0x00000011 (17)...

...data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to host port 22. debug1: Connection established. debug3: Not a RSA1 key file /usr/apps1/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace deb...

...gress/unittests/hostkeys/test_iterate.c index 2eaaf06..da0e353 100644 --- a/regress/unittests/hostkeys/test_iterate.c +++ b/regress/unittests/hostkeys/test_iterate.c @@ -92,12 +92,22 @@ check(struct hostkey_foreach_line *l, void *_ctx) #ifndef WITH_SSH1 if (parse_key && (expected->l.keytype == KEY_RSA1 || - expected->no_parse_keytype == KEY_RSA1)) { + expected->no_parse_keytype == KEY_RSA1)) { expected_status = HKF_STATUS_INVALID; expected_keytype = KEY_UNSPEC; parse_key = 0; } #endif +#ifndef WITH_OPENSSL + if (expected->l.keytype == KEY_RSA || + exp...

...ort will not be trusted. debug2: ssh_connect: needpriv 0 debug1: Connecting to www.schuldei.org [195.37.106.41] port 22. debug1: Connection established. debug3: Not a RSA1 key file /home/andreas/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing...

...eedpriv 0 debug1: Connecting to northstar [192.168.99.2] port 22. debug1: Connection established. debug1: identity file /Users/peter/.ssh/identity type 0 debug3: Not a RSA1 key file /Users/peter/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing...

On Thu, 11 Oct 2018, Adam Eijdenberg wrote: > On Thu, Oct 11, 2018 at 12:13 PM Damien Miller <djm at mindrot.org> wrote: > > Could you try this? > > > > diff --git a/sshconnect2.c b/sshconnect2.c > > index f104408..1d2906f 100644 > > --- a/sshconnect2.c > > +++ b/sshconnect2.c > > @@ -1080,7 +1080,8 @@ key_sig_algorithm(struct ssh *ssh, const

https://bugzilla.mindrot.org/show_bug.cgi?id=2455 Bug ID: 2455 Summary: Regression tests tweaks: keyscan and hostkey_rotation Product: Portable OpenSSH Version: 7.1p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Regression tests Assignee:

...: Connecting to host.server.com [16.245.97.226] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/3 debug1: identity file /.ssh/identity type 0 debug3: Not a RSA1 key file /.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace deb...

Hi Xen Users, I would like to boot into a knoppix iso on an existing domU. In my config file i have: disk = [ "file:/var/lib/xen/images/machine-10.img,hda,w","file:/mnt/knoppix.iso, hdb:cdrom,hdb,r" ] Can''t seem to boot it though. Do I have to go into the VMs BIOS to tell it to boot it? Cheers CHris _______________________________________________ Xen-users

...key: RSA-CERT SHA256:xxx /path/to/key > > debug1: send_pubkey_test: no mutual signature algorithm > > That looks like a bug: > > diff --git a/sshkey.c b/sshkey.c > index f7c09fb..e602987 100644 > --- a/sshkey.c > +++ b/sshkey.c > @@ -109,9 +109,9 @@ static const struct keytype keytypes[] = { > { "ssh-rsa-cert-v01 at openssh.com", "RSA-CERT", NULL, > KEY_RSA_CERT, 0, 1, 0 }, > { "rsa-sha2-256-cert-v01 at openssh.com", "RSA-CERT", > - "ssh-rsa-sha2-256", KEY_RSA_CERT, 0, 1,...

Hi, One of our users who is running an OS (I think it's the latest beta macOS 10.14.1) with ssh version "OpenSSH_7.8p1, LibreSSL 2.7.3" is unable to use our user SSH RSA certificates to authenticate to our servers (which are running "OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017"). We see this error on the client side: debug1: kex_input_ext_info:

On Thu, Sep 21, 2017 at 02:22:10AM -0500, Zev Weiss wrote: > test_kex: regress/unittests/kex/test_kex.c:91 test #1 "sshkey_generate" > ASSERT_INT_EQ(sshkey_generate(keytype, bits, &private), 0) failed: > sshkey_generate(keytype, bits, &private) = -56 That error code is: $ grep -- -56 ssherr.h #define SSH_ERR_KEY_LENGTH -56 Unfortunately there's lots of places in that code that can return that. I have seen that on one Cygwin system (OpenSSL 1.0.2k)...

...nect: needpriv 0 debug1: Connecting to server [x.x.x.x] port 22. debug1: Connection established. debug1: identity file /home/cdr/.ssh/identity type -1 debug3: Not a RSA1 key file /home/cdr/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whites...

...7.128.213.56[47.128.213.56] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/root/.ssh/identity type 0 debug3: Not a RSA1 key file /home/root/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'Proc-Type:' debug3: key_read: missing keytype debug2: key_type_from_name: unknown key type 'DEK-Info:' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing...