Hello!
A bug report about Buteo not syncing with Google via https [1] showed
that Qt tries to load OpenSSL libraries, which fails because they are
not installed where they are expected [2]. There is an open request to
change that [3].
First, is someone working on 7813? The original issue # wa
Em Quarta-feira, 8 de Dezembro de 2010, às 09:51:18, Patrick Ohly escreveu:
> A bug report about Buteo not syncing with Google via https [1] showed
> that Qt tries to load OpenSSL libraries, which fails because they are
> not installed where they are expected [2]. There is an open request to
> chan
On Mi, 2010-12-08 at 10:17 +, Thiago Macieira wrote:
> Em Quarta-feira, 8 de Dezembro de 2010, às 09:51:18, Patrick Ohly escreveu:
> > A bug report about Buteo not syncing with Google via https [1] showed
> > that Qt tries to load OpenSSL libraries, which fails because they are
> > not installe
ick.o...@intel.com]
Sent: Wednesday, December 08, 2010 12:30 PM
To: Thiago Macieira
Cc: meego-dev@meego.com
Subject: Re: [MeeGo-dev] Qt uses OpenSSL, and fails?
On Mi, 2010-12-08 at 10:17 +, Thiago Macieira wrote:
> Em Quarta-feira, 8 de Dezembro de 2010, às 09:51:18, Patrick Ohly escreveu:
> >
Hi,
Patrick Ohly wrote:
> Second, as mentioned in # and elsewhere [4], there is a license
> conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at
> runtime really work around this conflict? I'm not a lawyer, but given
> that the way how linking is achieved is typically not spe
On Wednesday 08 December 2010 15:39:26 ext Dave Neary, you wrote:
> Patrick Ohly wrote:
> > Second, as mentioned in # and elsewhere [4], there is a license
> > conflict between OpenSSL and GPL. Does opening OpenSSL via dlopen() at
> > runtime really work around this conflict? I'm not a lawyer,
On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote:
- use GnuTLS or NSS instead of OpenSSL,
we should be using NSS anyway wherever possible, not just for the
licensing side,
but also because openssl has a history of ABI mess.
___
MeeGo-dev mailing li
On 12/8/2010 3:00 AM, fathi.bou...@nokia.com wrote:
Hi,
The fix is in MeeGo 1.1 but still not in Trunk.
how on earth did that happen???
things are not allowed to go into 1.1 updates until the fix is in Trunk!
___
MeeGo-dev mailing list
MeeGo-dev@m
Em Quarta-feira, 8 de Dezembro de 2010, às 08:49:30, Arjan van de Ven
escreveu:
> On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote:
> > - use GnuTLS or NSS instead of OpenSSL,
>
> we should be using NSS anyway wherever possible, not just for the
> licensing side,
> but also because openssl has a his
Hi,
On Wed, Dec 8, 2010 at 21:44, Thiago Macieira wrote:
> Em Quarta-feira, 8 de Dezembro de 2010, às 08:49:30, Arjan van de Ven
> escreveu:
>> On 12/8/2010 8:44 AM, Rémi Denis-Courmont wrote:
>> > - use GnuTLS or NSS instead of OpenSSL,
>>
>> we should be using NSS anyway wherever possible, not
On Thu, 2010-12-09 at 14:35 +0200, Alexander Bokovoy wrote:
> > NSS is an alternative, but I think our legal department ruled out any Qt-NSS
> > code a while ago. I remember this because when the LSB wanted to standardise
> > on NSS, we reported we could never use it. I don't know if the circumstan
On Thu, Dec 16, 2010 at 10:24, David Woodhouse wrote:
>> More to that, OpenSSL since late 0.9 versions has proper support to
>> load crypto engines supporting other cryptography schemes. In
>> particular, this is important for supporting Russian and Chinese
>> cryptography standards. Neither of co
12 matches
Mail list logo
