The problem with these debdiffs is that we don't ship new versions of
packages as stable updates, they would have to land as backports. Stable
updates would require just applying
https://github.com/resiprocate/resiprocate/commit/645c9f461ca6e2d9d5167cc9c0ca4781c3e7c19b.
Is there any way to apply just that one commit for Trusty?
Also, for Utopic, why is there also 0002-client-avoid-TLSv1_2.patch? I
may be a little nitpicky here, but it sounds slightly different than
removing the hard-coded use of TLSv1 if we're also purposefully avoiding
TLSv1.2 servers. I agree it makes sense, but it feels like it probably
should be fixing a separate bug, since the symptoms would be different.
What do you think? This seems to me as one case where the change is "on
the line", especially if one doesn't understand OpenSSL and TLS well
enough.
I'll go ahead and mark the general (vivid) task as Fix Released since
resiprocate has been synced from unstable, so we already have 1:1.9.7-4
there.
Thanks!
** Changed in: resiprocate (Ubuntu)
Status: New => Fix Released
** Changed in: resiprocate (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: resiprocate (Ubuntu Utopic)
Importance: Undecided => Medium
** Changed in: resiprocate (Ubuntu Trusty)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1420956
Title:
hard-coded to use OpenSSL TLSv1_method
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resiprocate/+bug/1420956/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
