search for: sha256withrsaencrypt

...lish and many thanks! Enrico Extracted content of Let?s Encrypt CA is: [root at glusterfs1 ssl]# openssl x509 -in glusterfs.ca -text -noout Certificate: Data: Version: 3 (0x2) Serial Number: 0a:01:41:42:00:00:01:53:85:73:6a:0b:85:ec:a7:08 Signature Algorithm: sha256WithRSAEncryption Issuer: O=Digital Signature Trust Co., CN=DST Root CA X3 Validity Not Before: Mar 17 16:40:46 2016 GMT Not After : Mar 17 16:40:46 2021 GMT Subject: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3 Subject Public Key Info:...

I've installed LE certs on my Dovecot a while back, and, it has been working OK since, but, today, an iPhone user said he can't get emails as iphone says 'cert is expired', searching around, I see some other iPhone similar issues reported, do I have my conf correct, I have; # cat dovecot.conf | grep ssl ssl = required verbose_ssl = no ssl_cert =

...he address of your dovecot server, I tried openssl s_client -connect sbt.net.au:143 -starttls imap And received a cert which includes: Certificate: Data: Version: 3 (0x2) Serial Number: 03:5b:41:a6:f4:a6:33:eb:5b:ac:af:b8:20:96:f4:0e:20:b9 Signature Algorithm: sha256WithRSAEncryption Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3 Validity Not Before: Apr 23 11:11:28 2018 GMT Not After : Jul 22 11:11:28 2018 GMT Subject: CN=geko.sbt.net.au <http://geko.sbt.net.au/> Dovecot is sending an expired cert...

...vecot server, I tried > > openssl s_client -connect sbt.net.au:143 -starttls imap > > And received a cert which includes: > > > Certificate: > Data: > Version: 3 (0x2) > Serial Number: > 03:5b:41:a6:f4:a6:33:eb:5b:ac:af:b8:20:96:f4:0e:20:b9 > Signature Algorithm: sha256WithRSAEncryption > Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3 > Validity > Not Before: Apr 23 11:11:28 2018 GMT > Not After : Jul 22 11:11:28 2018 GMT > Subject: CN=geko.sbt.net.au <http://geko.sbt.net.au/> > > > > Dovecot is sending an expired cert. Pa...

Hello I am running https://radio.horsens-garage.rocks:8443. The SSL- certificate is made like this: cat /etc/letsencrypt/live/horsens-garage.rocks/fullchain.pem /etc/letsencrypt/live/horsens-garage.rocks/privkey.pem > /etc/icecast2/bundle.pem I have had no errors or warnings in any browser. Until now! Fulguris, a FOSS-browser for android, gave me a warning about invalide date in the

...a SAN so that should be fine. Serial numbers are the same: --- Common name: horsens-garage.rocks SANs: horsens-garage.rocks, radio.horsens-garage.rocks, www.horsens-garage.rocks Valid from June 9, 2024 to September 7, 2024 Serial Number: 03d86c7828fdae42b7d00f7159e11df15a36 Signature Algorithm: sha256WithRSAEncryption Issuer: R10 --- However, going to the radio.horsens-garage.rocks URL in Firefox renders that your cert is expired: Did you replace the cert on Icecast and not reload? Cheers, Jordan Erickson -- https://subj.am/ -------------- next part -------------- An HTML attachment was scrubbed... URL: &...

I have self certified Dovecot as so: ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } in order for end user to avoid webmail warnings or email client warnings, do I make this file /etc/pki/dovecot/certs/dovecot.pem available to users say under

...[2013-12-12 08:55:39] INFO WEBrick 1.3.1 [2013-12-12 08:55:39] INFO ruby 1.9.3 (2013-06-27) [x86_64-linux] [2013-12-12 08:55:39] DEBUG TCPServer.new(0.0.0.0, 8140) [2013-12-12 08:55:39] INFO Certificate: Data: Version: 3 (0x2) Serial Number: 10 (0xa) Signature Algorithm: sha256WithRSAEncryption Issuer: CN=Puppet CA generated on savbu-razor-server.cisco.com at 2013-12-10 05:05:10 -0800 Validity Not Before: Dec 11 16:55:39 2013 GMT Not After : Dec 11 16:55:39 2018 GMT Subject: CN=10.193.174.38 Subject Public Key Info: P...

.../easyrsa/private/MAIL.key > /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt > > $ openssl x509 -text -in /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt > > Certificate: > Data: > Version: 3 (0x2) > Serial Number: 1 (0x1) > Signature Algorithm: sha256WithRSAEncryption > Issuer: CN=mail.hprs.local > Validity > Not Before: Jul 2 05:54:26 2016 GMT > Not After : Jun 30 05:54:26 2026 GMT > Subject: CN=mail.hprs.local > Subject Public Key Info: > Public Key Algorithm: r...

...PRS/easyrsa/private/ca.key /etc/ssl/certs/OHPRS/easyrsa/private/MAIL.key /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt $ openssl x509 -text -in /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt Certificate: Data: Version: 3 (0x2) Serial Number: 1 (0x1) Signature Algorithm: sha256WithRSAEncryption Issuer: CN=mail.hprs.local Validity Not Before: Jul 2 05:54:26 2016 GMT Not After : Jun 30 05:54:26 2026 GMT Subject: CN=mail.hprs.local Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (...

.../easyrsa/private/MAIL.key > /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt > > $ openssl x509 -text -in /etc/ssl/certs/OHPRS/easyrsa/issued/dovecot.crt > > Certificate: > Data: > Version: 3 (0x2) > Serial Number: 1 (0x1) > Signature Algorithm: sha256WithRSAEncryption > Issuer: CN=mail.hprs.local > Validity > Not Before: Jul 2 05:54:26 2016 GMT > Not After : Jun 30 05:54:26 2026 GMT > Subject: CN=mail.hprs.local > Subject Public Key Info: > Public Key Algorithm: r...

OK, let me go through exactly what you did: you: > Here's the test (I must run mutt not telnet like i mentioned earlier to > get the imap tickets). > > root at server:~# kinit achim > Password for achim at DOMAIN.LOCAL: > [I enter my password] As root on AD/DC mail.hprs.local: me: $ kinit mark Password for mark at HPRS.LOCAL: [I enter my password] you: >