search for: sha1withrsaencryption

...=> Ctrl-C to shutdown [2010-03-04 17:27:22] INFO WEBrick 1.3.1 [2010-03-04 17:27:22] INFO ruby 1.8.6 (2007-09-24) [i486-linux] [2010-03-04 17:27:22] INFO Certificate: Data: Version: 1 (0x0) Serial Number: 80:f2:ab:75:5a:02:94:d7 Signature Algorithm: sha1WithRSAEncryption Issuer: C=US,.... stuff Validity Not Before: Mar 3 18:28:16 2010 GMT Not After : Feb 29 18:28:16 2020 GMT Subject: C=US, .......stuff Subject Public Key Info: Public Key Algorithm: rsaEncryption RSA Public Key:...

...reduced my CA and CASSL keys from 2048 down to 1024... not sure if it helped, but I don't have this error anymore... How can I check if the crl.pem file is ok? $ openssl crl -in cassl/crl.pem -text Certificate Revocation List (CRL): Version 1 (0x0) Signature Algorithm: sha1WithRSAEncryption Issuer: /C=AA/ST=BB/L=CC/O=DD/CN=myhost.mydomain Last Update: Nov 4 14:39:36 2009 GMT Next Update: Nov 4 14:39:36 2010 GMT Revoked Certificates: Serial Number: 02 Revocation Date: Nov 4 14:37:03 2009 GMT Signature Algorithm: sha1WithRSAEncryp...

Hi: I''m trying to configure Puppet on Ubuntu, and strangely I am never able to generate a certificate because my server never shows any pending certificate requests. Put differently, on the server I am running puppetmasterd and on the client I am able to connect to the server, but the client continues printing notice: Did not receive certificate warning: peer certificate

...the time is in sync. # date Wed Feb 27 08:04:36 GMT 2013 This is on the client which is the same as all the rest of the Linux clients. # openssl x509 -text -in /etc/puppet/ssl/certs/ca.pem Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha1WithRSAEncryption Issuer: CN=Puppet CA: <PUPPETMASTER-FQDN> Validity Not Before: Dec 28 11:11:33 2011 GMT Not After : Dec 27 11:11:33 2016 GMT Subject: CN=Puppet CA: <PUPPETMASTER-FQDN> These are using the OpenCSW Solaris packages. I cannot work out why t...

Hello, Attempting to setup a CA primary/standby as well as seperate puppetmaster servers (all running Apache/Passenger) behind another Apache/Passenger type load balancer. Clients are not getting certs:- err: Could not request certificate: Could not intern from s: nested asn1 error Clearly an SSL issue but not something I know a great deal about. loadbalancer.conf # Puppet Load Balancing

...s:pbx.domain.com:5061 Authentication Username: 361 - - - [ Setup > Certificates > Server Certificates ] Country: ; State: ; Locality ; Organization: ; Common Name: pbx.domain.com; eMail: Version: 2 Serial Number: 00b6b63eb67ed2111345253c228264d093 Signature Algorithm: 1.2.840.113549.1.1.5 (sha1WithRSAEncryption) Signature: 28ce574c9715e1e59dfc90829287ab31fdbf0e0212dc488b106e71ffaaa339610492dc091d440772... Issuer: Country: GB; State: Greater Manchester; Locality Salford; Organization: Comodo CA Limited; Common Name: PositiveSSL CA; eMail: Validity: 27/04/11 - 26/04/12 SHA1-Fingerprint: 38d13c709ab1cc9b434c...

...known and matches the RSA+cert host key. debug1: Found key in /root/.ssh/known_hosts:1 debug2: bits set: 495/1024 debug3: ssh_x509_verify: signature key type = x509v3-sign-rsa debug3: ssh_x509_verify: evp_md { 4(md5), 8(md5WithRSAEncryption), 16, ... } debug3: ssh_x509_verify: evp_md { 64(sha1), 65(sha1WithRSAEncryption), 20, ... } !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ssh_x509_verify: verify failed: error:0D09B0A3:asn1 encoding routines:d2i_PublicKey:unknown public key type debug3: ssh_x509_verify: return 0 key_verify failed for server_host_key !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! #########...