Sam Hartman writes:
> can we (Debian) support SSL 1.1 with Shibboleth?
> That is, are the patches something you're comfortable integrating as
> Debian?
I haven't seen the latest iteration of the Santuario compatibility
patches yet. Judging by the earlier glimpses, they are
So,
can we (Debian) support SSL 1.1 with Shibboleth?
That is, are the patches something you're comfortable integrating as
Debian?
On 12/4/16, 4:00 PM, "Ferenc Wagner,,, on behalf of Ferenc Wágner"
wrote:
> Sure you did, and nobody blames you (I hope my mail didn't come through
> like that).
No, it didn't.
Didn't Debian at one time support simultaneous installation of libcurl built on
both NSS and
"Cantor, Scott" writes:
> Didn't Debian at one time support simultaneous installation of libcurl
> built on both NSS and OpenSSL?
It still does.
> Can't they just provide a libcurl for both OpenSSL versions, with
> appropriate naming changes?
I think that would be possible,
"Cantor, Scott" writes:
> On 12/4/16, 11:09 AM, wf...@niif.hu wrote:
>
>> I can't see any conclusion in the OpenSSL 1.1 thread on debian-devel,
>> but we're running out of time. We can't keep XMLTooling at OpenSSL
>> 1.0, because libcurl uses 1.1, but we can't switch to 1.1
On 12/4/16, 11:09 AM, "Pkg-shibboleth-devel on behalf of Ferenc Wágner"
wrote:
> I can't see any conclusion in the OpenSSL 1.1 thread on debian-devel,
>but we're running out of time. We can't
Russ Allbery writes:
> wf...@niif.hu (Ferenc Wágner) writes:
>
>> Just adding that Shibboleth itself is also problematic, because
>> XMLTooling, which is incompatible with OpenSSL 1.1, uses libcurl,
>> which already switched to OpenSSL 1.1. So switching xml-security-c
>> to
hi,
so as it seems either my mirror was lagging or my cowbuilder failed on
the update - but with the recent upload of libxml-security-c-dev using
1.0 I can build open-vm-tools. which will work for now - as long as no
other dependency hell will arise.
best regards,
bernd
--
Bernd Zeimetz
> It's worth noting that Apache also requires OpenSSL 1.0, which may also
> affect what the Shibboleth stack can link against.
No, that code is isolated into shibd, mod_shib doesn't link to it. That was
deliberate of course, for exactly this reason.
There are edge cases. If you link Xerces to
wf...@niif.hu (Ferenc Wágner) writes:
> Just adding that Shibboleth itself is also problematic, because
> XMLTooling, which is incompatible with OpenSSL 1.1, uses libcurl, which
> already switched to OpenSSL 1.1. So switching xml-security-c to OpenSSL
> 1.0 did not actually solve the problem for
Russ Allbery writes:
> Bernd Zeimetz writes:
>
>> unfortunately your decision to depend on libssl1.0-dev breaks the build
>> open-vm-tools as most other build-dependencies decided to migrate to
>> the new openssl version.
>
>> I know that shibboleth is the
Bernd Zeimetz writes:
> unfortunately your decision to depend on libssl1.0-dev breaks the build
> open-vm-tools as most other build-dependencies decided to migrate to
> the new openssl version.
> I know that shibboleth is the issue, but the current situation breaks
>
Package: libxml-security-c-dev
Version: 1.7.3-4
Severity: serious
Hi,
unfortunately your decision to depend on libssl1.0-dev breaks the build
open-vm-tools as most other build-dependencies decided to migrate to
the new openssl version.
I know that shibboleth is the issue, but the current
13 matches
Mail list logo