The upstream changes are still not good enough, it doesn't verify that
the configured server hostname matches a name on the certificate.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374729
Title:
** Changed in: up-imapproxy (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374729
Title:
X509 certificate verification problem
To manage notifications
[Expired for up-imapproxy (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: up-imapproxy (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We have contacted the upstream and check out their latest SVN. We are
sure that IMAPproxy in Ubuntu packages(all version) is vulnerable due to
the missing of SSL certificate validation. This is fixed in the upstream
on Jan 20th 2014. Please check their latest version, the changes are
mainly in
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1374729
Title:
X509 certificate verification problem
To manage notifications about this bug
