search for: newkey

Hi, I have a question about llvm/ADT/DenseMap.h and llvm/IR/ValueMap.h: When you have a: MapType M; is it safe to do: M[NewKey] = M[OldKey]; or do you need to do it in two steps: auto tmp = M[OldKey]; // ensure the reference to M[OldKey] is copied, before reassigning. M[NewKey] = tmp; // might reallocate aka, will a possible allocation for M[NewKey] invalidate the reference that M[OldKey] returns ? Greetings...

...<tm>. The local socket is just a > socket, and the protocol[1] message SSH_AGENT_ADD_KEY is the same. Local: $ ssh-agent > /tmp/agent.env $ source /tmp/agent.env $ ssh-add ~/.ssh/id_user $ ssh -A remote Remote: $ SSH_AUTH_SOCK=/tmp/ssh-1rVbCSbuDP/agent.3145 $ ssh-add newkey Identity added: newkey (newkey) Local: $ source /tmp/agent.env $ ssh-add -l 2048 SHA256:32C...qYBs /home/user/.ssh/id_user (RSA) 2048 SHA256:32C...qYBs /home/user/.ssh/id_user (RSA-CERT) 2048 SHA256:SZG...5hUQ newkey (RSA) That worked perfectly, it seems. > > Is such an operation...

...r information from the server using the 'logit' function. For example, I'm trying to get the cipher, mac, and compression status from kex.c in kex_chose_conf() with logit("SSH: %s;Ltype: Kex;Enc: %s;MAC: %s:Comp: %s", ctos ? "Server" : "Client", newkeys->enc.name, newkeys->mac.name, newkeys->comp.name); right after the similar debug statement. When I'm running the server in debug mode this line works fine. However, when I use it in normal mode this information doesn't print out at all. I'm assuming this has somethin...

...with GCC; Clang dereferenced the right hand side reference before evaluating the left hand side, as long as the value type was as small as the reference itself. // Martin On Thu, 26 Sep 2019, David Blaikie via llvm-dev wrote: > Yep - You'd have to separate them for correctness if "NewKey" might not > already be in "M". > > On Thu, Sep 26, 2019 at 2:48 PM Jeroen Dobbelaere via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > Hi, > > I have a question about llvm/ADT/DenseMap.h and > llvm/IR/ValueMap.h: > > Wh...

...ion, but however i am following all howtos and tutorials it is not working 1) i have created CA certificate - /etc/pki/tls/misc/CA -newca 2) i have generated a new request - /etc/pki/tls/misc/CA -newreq 3) i have signed certificate /etc/pki/tls/misc/CA -signreq SO i have CA in /etc/pki/CA i have newkey.pem i have newcert.pem i have also cealrkey.pem (without passphrase) *$ openssl rsa < newkey.pem > clearkey.pem* What to do next?? What to put in slapd.conf in order to make it work?? What to put in ldap.conf in order to communicate Really thanks in advance!! David -------------- next par...

...s256-cbc hmac-sha1 none debug: kex: server->client aes256-cbc hmac-sha1 none debug: SSH2_MSG_KEX_DH_GEX_REQUEST_OLD received debug: SSH2_MSG_KEX_DH_GEX_GROUP sent debug: expecting SSH2_MSG_KEX_DH_GEX_INIT debug: SSH2_MSG_KEX_DH_GEX_REPLY sent debug: kex_derive_keys........................ debug: newkeys[1]=0xfd4868 debug: SSH2_MSG_NEWKEYS sent debug: expecting SSH2_MSG_NEWKEYS debug: newkeys[0]=0xfd4748 debug: SSH2_MSG_NEWKEYS received debug: userauth-request for user terter service ssh-connection method none debug: attempt 0 failures 0 debug: userauth-request for user terter service ssh-connecti...

...ebug1: SSH2_MSG_KEX_DH_GEX_REQUEST received debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent debug1: dh_gen_key: priv key bits set: 121/256 debug1: bits set: 1614/3191 debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT debug1: bits set: 1588/3191 debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user quinot service ssh-connection method none debug1: attempt 0 failures 0 Fa...

Is this a known issue? (ignore the pervasive MS-outlook capitalization) Ssh-agent /bin/ksh Ssh-add /root/.ssh/id_rsa Blah blah Ssh -vvv some_server date ... debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERV...

...CURE SSH SNL1.0 debug1: match: 3.0.1 F-SECURE SSH SNL1.0 pat 3.0.* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.5p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received . . . but it fails near the end like this: . . . debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that c...

...SG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '192.168.1.111' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:41 debug1: bits set: 1556/3191 debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authenticatio...

...h various of external application expects PKCS#1 encoded key, while many applications use SubjectPublicKeyInfo encoded key. This change adds SubjectPublicKeyInfo support, to ease integration with applications. Examples: ## convert SubjectPublicKeyInfo public key to SSH public key $ openssl req -newkey rsa:2048 -nodes -pubkey -subj "/CN=test" \ -noout -keyout /dev/null | \ ssh-keygen -i -m SUBJECTINFO -f /proc/self/fd/0 ## convert X.509 certificate to SSH public key $ openssl req -newkey rsa:2048 -nodes -x509 -subj "/CN=test" \ -keyout /dev/null | openssl x509 -pub...

I am trying to automate ssh-keygen creating keys without a passphrase. How can I run a script that calls ssh-keygen so that it does NOT require a passphrase? When I was testing on the command line I created a file that contained 2 line feeds and piped it into stdin. I got a message mentioning that ssh-askpass could not be found and it completed. I did not try the keys but I would like to be

Hello all, What are the instructions for making an SSL cert for Dovecot IMAPS? Two methods have been tried, and work, with Evolution; however generate the following error when Thunderbird tries to connect. Thank you, method 1 : self signed openssl req -newkey rsa:4096 -sha512 -x509 -days 365 -nodes -keyout mykey.key -out mycert.pem method 2 : Let's Encrypt (LE) CA Created with Certbot ERROR TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<+oooooo&gt...

Apologies if this post is inappropriate to this list; please redirect me if so. Our team uses ssh extensively for server access and maintenance (Debian). An issue is acting as root when operating, for example, over ansible and keeping a record of who performed the actions, something ssh certificates solves well. The problem is then to automate certificate issuance since it would be pretty

I made a special pair of keys just for Icecast with this command: $ openssl req -newkey rsa:2048 -new -nodes -x509 -days 3650 -keyout key.pem -out cert.pem I combined the two files like this: $ cat cert.pem key.pem > icecast.pem I placed icecast.pem in /etc/icecast2 and used 'chown icecast2:icecast icecast.pem' to change owner to icecast2:icecast. I also changed its p...

...ved > debug1: SSH2_MSG_KEX_DH_GEX_GROUP sent > debug1: dh_gen_key: priv key bits set: 134/256 > debug1: bits set: 1602/3191 > debug1: expecting SSH2_MSG_KEX_DH_GEX_INIT > debug1: bits set: 1528/3191 > debug1: SSH2_MSG_KEX_DH_GEX_REPLY sent > debug1: kex_derive_keys > debug1: newkeys: mode 1 > debug1: SSH2_MSG_NEWKEYS sent > debug1: waiting for SSH2_MSG_NEWKEYS > debug1: newkeys: mode 0 > debug1: SSH2_MSG_NEWKEYS received > debug1: KEX done > debug1: userauth-request for user cheekoon service ssh-connection method > none > debug1: attempt 0 failures 0 &...

...: : waiting for MONITOR_ANS_SIGN debug3: entering: type 5 debug3: entering debug3: : checking request 4 debug3: debug3: : signature 4002f878(143) debug3: entering: type 5 debug2: : 4 used once, disabling now debug1: SSH2_MSG_KEX_DH_GEX_REPLY sentdebug3: entering debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: KEX done debug1: userauth-request for user root service ssh-connection method none debug1: attempt 0 failures 0 debu...

...cting SSH2_MSG_KEX_DH_GEX_REPLY bits set: 1573/3191 ********* 4.260 seconds ********* 4.730 seconds SSH2_MSG_KEX_DH_GEX_REPLY sent check_host_in_hostfile kex_derive_keys Host 'xx' is known and matches RSA key newkeys: mode 1 bits set: 1582/3191 SSH2_MSG_NEWKEYS sent ********* 3.910 waiting for SSH2_MSG_NEWKEYS ssh_rsa_verify: signature correct kex_derive_keys newkeys: mode 1 SSH2_MSG_NEWKEYS sent waiting for SSH2_MSG_NEWKEYS ********* 4.110 newkeys: mod...

...SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '147.101.224.39' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts2:2 debug1: bits set: 1063/2049 debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: done: ssh_kex2. debug1: send SSH2_MSG_SERVICE_REQUEST debug1: service_accept: ssh-userauth debug1: got SSH2_MSG_SERVICE_ACCEPT debug1: authentications that c...

Hi, I am trying to run openssh 3.1p1. But it is giving "Bad packet length" error when I run sshd with default config file. On further investigation I found that the error is coming only for the cipher algorithm "aes128-cbc". Also the error comes only when I don't specify any protocol file (/usr/local/etc/ssh_host_[rd]sa_key) or specify only "protocol 2" files. I