Mikkel Krautz:
> On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle
> wrote:
>> Mikkel Krautz:
>>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
I would also like to say again that if we can somehow see in the
meta data that they are using
Kurt Roeckx:
> On Mon, Mar 14, 2016 at 10:25:30PM +0100, Mikkel Krautz wrote:
>> Quoting Kurt Roeckx:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get rebuild at
>>> the same time and you wouldn't get into this situation
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle
wrote:
>> Mikkel Krautz:
>>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
I would also like to say again that if we can somehow see in the
meta data that they are using
On Mon, Mar 14, 2016 at 10:25:30PM +0100, Mikkel Krautz wrote:
> Quoting Kurt Roeckx:
> > I would also like to say again that if we can somehow see in the
> > meta data that they are using libssl, they would get rebuild at
> > the same time and you wouldn't get into this situation that they
> >
On Sun, Mar 13, 2016 at 6:20 PM, Chris Knadle wrote:
> Mikkel Krautz:
>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get
On Sun, Mar 13, 2016 at 9:20 PM, Chris Knadle wrote:
> Mikkel Krautz:
>> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>>> I would also like to say again that if we can somehow see in the
>>> meta data that they are using libssl, they would get
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time and you wouldn't get into this situation that they
>> are
Chris Knadle:
> Mikkel Krautz:
>[...]
> When a new OpenSSL comes down containing a library rename, the Mumble #2124
> patch will disallow multiple libssl/libcrypto load and Mumble will break.
> Besides Mumble not being functional, the broken behavior deletes the user's
> SSL key used with Mumble
Mikkel Krautz:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time and you wouldn't get into this situation that they
>> are
On Sun, Mar 13, 2016 at 4:18 PM, Kurt Roeckx wrote:
> On Sun, Mar 13, 2016 at 03:55:54PM +0100, Mikkel Krautz wrote:
>> On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
>> > On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
>> >> A tiny bit of
On Sun, Mar 13, 2016 at 03:55:54PM +0100, Mikkel Krautz wrote:
> On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
> > On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
> >> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
> >>
> >> In the
On Sun, Mar 13, 2016 at 3:36 PM, Kurt Roeckx wrote:
> On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
>> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
>>
>> In the earlier Debian bug that was linked by Chris, it was brought up
>> that
On Sun, Mar 13, 2016 at 03:28:30PM +0100, Mikkel Krautz wrote:
> A tiny bit of follow-up to my suggestion of using "-openssl-linked" for Qt:
>
> In the earlier Debian bug that was linked by Chris, it was brought up
> that an application may use QtNetwork without using SSL, and therefore
> might
On Sun, Mar 13, 2016 at 3:22 PM, Mikkel Krautz wrote:
> On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
>> I would also like to say again that if we can somehow see in the
>> meta data that they are using libssl, they would get rebuild at
>> the same time
On Sun, Mar 13, 2016 at 2:58 PM, Kurt Roeckx wrote:
> I would also like to say again that if we can somehow see in the
> meta data that they are using libssl, they would get rebuild at
> the same time and you wouldn't get into this situation that they
> are using a different
On Sun, Mar 13, 2016 at 01:57:23PM +0100, Mikkel Krautz wrote:
> On Sat, Mar 12, 2016 at 8:06 PM, Kurt Roeckx wrote:
> > On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
> >> > Maybe Qt should have some way to indicate what version it's build
> >> > against so that we
On Sat, Mar 12, 2016 at 11:38 AM, Kurt Roeckx wrote:
> On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
>> Discussions with mumble upstream about this problem have continued, and the
>> situation seems much more muddied than I previously knew. This is likely
>> not
On Sat, Mar 12, 2016 at 8:06 PM, Kurt Roeckx wrote:
> On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
>> > Maybe Qt should have some way to indicate what version it's build
>> > against so that we can binNMU it with all the other packages? Or
>> > maybe Qt should
On Sat, Mar 12, 2016 at 04:56:22PM +, Chris Knadle wrote:
> > Maybe Qt should have some way to indicate what version it's build
> > against so that we can binNMU it with all the other packages? Or
> > maybe Qt should just link against it, instead of doing dlopen()?
>
> Mumble upstream
Kurt Roeckx:
> On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
>> Discussions with mumble upstream about this problem have continued, and the
>> situation seems much more muddied than I previously knew. This is likely
>> not an OpenSSL issue per se but rather seems to be an issue
On Sat, Mar 12, 2016 at 01:04:12AM +, Chris Knadle wrote:
> Discussions with mumble upstream about this problem have continued, and the
> situation seems much more muddied than I previously knew. This is likely
> not an OpenSSL issue per se but rather seems to be an issue whenever OpenSSL
>
On Mon, Nov 09, 2015 at 09:36:46PM +, Chris Knadle wrote:
> Kurt Roeckx:
> > On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
> >>
> >> Everybody dealing with the mumble bug agrees that SSL should be initialized
> >> before making SSL calls -- the reason I opened #804487 is to try
On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
>
> Everybody dealing with the mumble bug agrees that SSL should be initialized
> before making SSL calls -- the reason I opened #804487 is to try to figure
> out /what/ caused mumble_1.2.10-2+b1 to break, when mumble_1.2.10-2 works.
>
On Sun, Nov 08, 2015 at 10:26:42PM +, Chris Knadle wrote:
> Package: openssl
> Version: 1.0.2d-3
> Severity: serious
>
> Greetings.
>
> I'm marking this bug as 'serious' because the upgrade to 1.0.2d-3 seems to
> have broken mumble, though it's unclear why that would be.
>
> After a binNMU
Kurt Roeckx:
> On Sun, Nov 08, 2015 at 10:26:42PM +, Chris Knadle wrote:
>> Package: openssl
>> Version: 1.0.2d-3
>> Severity: serious
>>
>> Greetings.
>>
>> I'm marking this bug as 'serious' because the upgrade to 1.0.2d-3 seems to
>> have broken mumble, though it's unclear why that would be.
Kurt Roeckx:
> On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
>>
>> Everybody dealing with the mumble bug agrees that SSL should be initialized
>> before making SSL calls -- the reason I opened #804487 is to try to figure
>> out /what/ caused mumble_1.2.10-2+b1 to break, when
Kurt Roeckx:
> On Mon, Nov 09, 2015 at 09:36:46PM +, Chris Knadle wrote:
>> Kurt Roeckx:
>>> On Mon, Nov 09, 2015 at 07:58:30PM +, Chris Knadle wrote:
Everybody dealing with the mumble bug agrees that SSL should be initialized
before making SSL calls -- the reason I opened
27 matches
Mail list logo