Summary: | Claws presents 1y old certificate as new and asks for exchange | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Claws Mail (GTK 2) | Reporter: | codejodler | ||||||||
Component: | Other | Assignee: | users | ||||||||
Status: | RESOLVED WORKSFORME | ||||||||||
Severity: | normal | ||||||||||
Priority: | P3 | ||||||||||
Version: | 3.15.1 | ||||||||||
Hardware: | PC | ||||||||||
OS: | Linux | ||||||||||
URL: | https://posteo.de/site/impressum | ||||||||||
Attachments: |
|
For whatever reason, it appears that the posteo.de server presented you with an old certificate. Well, i exchanged several mails with them and they still insist that they really, really didn't. What are my options to get behind this ? There's nowhere to go with this. Claws Mail gets the certificate from the server. posteo say they didn't offer an old cert, so that's a stalemate. Created attachment 1837 [details]
Cert update request when receiving POP
Created attachment 1838 [details]
Cert update request when Sending POP
I agree it's a stalemate. I got the same issue todasy and asked the provider again about it. A couple of weeks ago, i asked Posteo if some weird type of man-in-the-middle could be involved, but they can't imagine. Do you think there could be something like this going on ? But i'm ok with closing the bug (for now). Your 2 latest screen shots don't show the same issue. They both look entirely expected - posteo have replaced the cert that expires on 22-Jan-18 with a new cert which expires on 22-Jan-19. Ah, uh ... sorry, apparently my mistake. At least now we know how it looks normally ... ;| Anyway, provider's launched now a regular 'cert change' page on their site, probably for hypocrites like me ... |
Created attachment 1813 [details] Certifificate change request (claws popup) Claws version 3.15.1-dirty on Debian Linux buster/sid (testing) POP account with defaults, and according to the posteo staff, correctly configured. A couple of days ago, claws presented me with this popup (attachment). I verified the keys on the posteo homepage To avoid confusion i should note that the dates in question are 2017-01-22 and 2018-01-22 (as in January 22nd). A call back on the posteo staff turned out that they had no cert change recently, and the 2018-01-22 one is already in use since long. I've no extra certs installed manually and i don't know why this is happening.