security release at some
point and I might upload it at that time.
Kurt
>
> Since
> https://piuparts.debian.org/stretch/source/o/openssl.html
>
> says "successfully-tested 1.1.0f-3" I think that we are done here.
I think it's other packages that call openssl from the maintainer
scripts that fail.
Kurt
it should
have been renamed ages ago.
Thijs, do you have time to do this?
Kurt
On Mon, Aug 28, 2017 at 12:24:17PM +0200, Bernhard Schmidt wrote:
> Am 26.08.2017 um 13:18 schrieb Kurt Roeckx:
>
> Hi Kurt,
>
> > Source: openvpn
> > Version: 2.4.3-4
> > Severity: important
> > Tags: patch
> >
> > Hi,
> >
> > T
point postfix upstream will add proper
support for the SSL_CTX_set_min_proto_version() way of setting
the minimum TLS version from the config file, I suggest you use
this patch until that time.
Kurt
--- src/tls/tls_server.c.bak 2017-08-26 18:12:06.356346925 +0200
+++ src/tls/tls_server.c 2017-08-26
is currently TLS 1.2 and
you can't override it with the options that you're currently using
(and are deprecated).
Kurt
--- src/openvpn/ssl_openssl.c.bak 2017-08-26 13:10:40.333428825 +0200
+++ src/openvpn/ssl_openssl.c 2017-08-26 13:12:05.143672978 +0200
@@ -215,6 +215,19 @@
#endif
On Sat, Aug 26, 2017 at 02:50:37PM +0800, Gedalya wrote:
> On 08/26/2017 02:58 AM, Kurt Roeckx wrote:
>
> > openvpn doesn't seem to make use of the
> > SSL_CTX_set_min_proto_version() function yet. I've attached a
> > patch that I didn't even try to compile that I think
r supporting only
> TLS 1.0, and it doesn't work. It did of course work with with openssl
> 1.1.0f-3.
> with 1.1.0f-5, I get:
openvpn doesn't seem to make use of the
SSL_CTX_set_min_proto_version() function yet. I've attached a
patch that I didn't even try to compile that I think should do the
against uscan to do this, I understand that it's
been commited just not uploaded yet.
Kurt
> (https://www.ssllabs.com/ssltest/viewClient.html?name=IE=8=XP=101)
>
> The cipher is still present in the ciphers(1ssl) manpage.
That cipher has been disabled by default because of the sweet32
attack. There are no ciphers enabled anymore that can talk to IE
on windows XP.
Kurt
y to continously
> test debian/unstable and debian/testing on servers in our environment.
I'm going to start with reassigning this to kmail. I believe all
such issues should get fixed, and that they should get fixed in
stable and maybe oldstable too.
I'm planning on making a change to openssl too, but it would still
likely still and up broken.
Kurt
y:
>
> SSLv23_method(), SSLv23_server_method() and SSLv23_client_method()
> were deprecated and the preferred TLS_method(), TLS_server_method()
> and TLS_client_method() functions were introduced in OpenSSL 1.1.0.
>
> Did I missunderstood something here?
Even tought it's deprecated, it's unlikely we'll remove the
compatiblity define any time soon. So either way really works for
me.
Kurt
On Sun, Aug 06, 2017 at 06:03:30PM +0200, Sebastian Andrzej Siewior wrote:
> On 5 August 2017 23:31:33 CEST, Kurt Roeckx <k...@roeckx.be> wrote:
>
> >I planned to break things by disabling TLS 1.0 and 1.1, which I
> >might upload soon. I guess I can fix that at the same
g new.
I planned to break things by disabling TLS 1.0 and 1.1, which I
might upload soon. I guess I can fix that at the same time.
Kurt
reassign 870018 kamailio
thanks
On Wed, Aug 02, 2017 at 05:01:01PM +0200, Guillem Jover wrote:
> Control: tags -1 patch
>
> Hi!
>
> On Sat, 2017-07-29 at 09:11:53 +0200, Kurt Roeckx wrote:
> > On Sat, Jul 29, 2017 at 12:12:16AM +0200, Michael Prokop wrote:
> > > Ku
r changelog entry.
I guess you don't have any patch for this?
Kurt
Can you confirm that this is problem with the test and not the RNG?
Kurt
On Sat, Jul 29, 2017 at 12:12:16AM +0200, Michael Prokop wrote:
>
> Kurt, do you have any ideas what might go wrong in OPENSSL_cleanup
> here and how this could be fixed? We'd appreciate any hints. Thanks!
I don't see anything obvious wrong. From what I understand it
calls exit(0) from
On Thu, Jul 27, 2017 at 08:14:45AM -0700, Daniel Schepler wrote:
> On Thu, Jul 27, 2017 at 12:02 AM, Kurt Roeckx <k...@roeckx.be> wrote:
> > Is that reproducible?
>
> Yes, it's definitely reproducible on my machine.
Does the attached patch
ut expected (7)
>Tests out of sequence. Found (9) but expected (8)
> Displayed the first 5 of 8 TAP syntax errors.
Is that reproducible?
This was most likely fixed upstream the day after the release.
Kurt
try to implement all the rules that
Mozilla applies in all software that deals with certificate. And
at least Mozilla is interested in that, and at least some of the
OpenSSL people would also like to see OpenSSL have more checks
than that currently happen.
Kurt
'
> and the like.
We have version 5.0.1-8~bpo8+1 of dose-builddebcheck installed,
while the bug indicates that it's fixed in 4.1-1.
Kurt
Apache 2.4.26 has been released which supports openssl 1.1.0.
Kurt
Package: firmware-misc-nonfree
Version: 20161130-3
Severity: important
Dear Maintainer,
I can't use edimax ew-7711usn device on debian stretch. I've loaded firmware-
misc-nonfree package. I'm seeing the device and wirelees networks in network
manager. But I can not connect to one of them.
;
> > Most bugs are in that case, so "wontfix" is improper. What matters
> > is that the bug will be fixed for the next stable version.
>
> I'm not sure whether we do want to split this up. If we don't plan to
> ever split it "wontfix" (and eventually closin
What matters
> is that the bug will be fixed for the next stable version.
>
> > For sid there is a new binary package sntp that ships a proper
> > ntp client.
>
> Unless sntp completely replaces ntpdc and ntpq, this doesn't solve
> the bug.
I think it's a replacement of ntpdate, not ntpdc and ntpq
Kurt
Greetings with Confidence
My name is Sgt. Martin Kurt currently serving in US military; I am
contacting you to help me on a fund transfer. In one of our
operations, some fund was discovered by my team and due to my position
here; I cannot leave the base as am still on assignment. Therefore, I
am
is issue be closed?
This issue has been reassigned to the openssl package, and it's not
fixed yet in Debian. There is nothing to do on the simple-tpm-pk11
side.
Kurt
On Mon, Jun 05, 2017 at 11:33:57AM +0200, Cyril Brulebois wrote:
> Kurt Roeckx <k...@roeckx.be> (2017-06-04):
> > So I've uploaded openssl 1.1.0f-2
>
> Source debdiff lgtm from -1, and installation over https works fine,
> ACK.
So I actually have a new version I want to u
y_)failed with error 22
But I can confirm that just upgrading libssl1.1 triggers the problem.
The only idea that I currently have is that it's related to a
cleanup handler after the program terminates.
Kurt
On Sun, Jun 04, 2017 at 06:53:29PM +0200, Cyril Brulebois wrote:
> Kurt Roeckx <k...@roeckx.be> (2017-06-04):
> > So I changed it this instead:
> > dh_makeshlibs -a -V --add-udeb="libcrypto1.1-udeb" -Xengines
> >
> > the shlib files now looks l
On Sun, Jun 04, 2017 at 11:09:00AM +, Niels Thykier wrote:
> Kurt Roeckx:
> > [...]
> >>
> >> Maybe file this as an RC bug against openssl so that it isn't forgotten
> >> about, but ignore it for r0?
> >
> > So I have prepared an update. Shoul
On Sun, Jun 04, 2017 at 05:29:21AM +0200, Cyril Brulebois wrote:
> Niels Thykier <ni...@thykier.net> (2017-06-03):
> > Kurt Roeckx:
> > > Package: release.debian.org
> > > User: release.debian@packages.debian.org
> > > Usertags: unblock
> > >
-0.2
Kurt
hat the package manager should be able
to deal with a conflict on just one side. It's not a conflict that
involves version numbers.
However, if everybody agrees that this is the best solution for
the next release, I will need permission from the release team
to make such a change.
Kurt
and they agreed it was
their problem and they fixed it.
See:
https://github.com/openssl/openssl/pull/3360#issuecomment-304053330
https://github.com/pyca/cryptography/commit/6e7ea2e73e3baf31541c9533dc621d8913152848
Kurt
processor
(Closes: #861145)
* Refresh valgrind.patch
Kurt
)
- Properly detect features on the AMD Ryzen processor
(Closes: #861145)
- Don't mention -tls1_3 in the manpage (Closes: #859191)
* Update libssl1.1.symbols for new symbols
* Update man-section.patch
Kurt
On Wed, May 24, 2017 at 10:42:14PM +, Hans Linkels wrote:
> Hi Kurt,
>
> I agree with you on both statements. Libcrypto is not being linked,
> and I have no idea either :)
>
> Today I installed the source files from the Jessie repo on a
> fairly pristine Jessie insta
On Wed, May 24, 2017 at 09:42:39AM +, Hans Linkels wrote:
> Hello Kurt,
>
> I have prepared the build according to the normal Debian procedure for
> building a package. This included running mk-build-deps. I checked the
> presence of libssl-dev. It is installe
ned
> reference to `CRYPTO_memcmp'
> collect2: error: ld returned 1 exit status
Do you have libssl-dev installed?
Kurt
penssl doesn't convert
> the string to UTCTime format.
Please note that the manual says the format is: YYMMDDHHMMSSZ
I guess it would be nice we converted it properly.
Kurt
tion
> of /bin/sh (which is an argument I'm still not buying) I see no
> downsides.
>
> Kurt, what do you think?
I guess systemd is happy with an exec(), that it stays the same
PID?
In that case I would prefer that we do it with a script, which
should be able to do the other things like adding the correct
user to run as.
Kurt
nd, installing the debug
> symbols for libssl1.0.2, I was able to get the following (not entirely
> complete, but hopefully, enough) bactrace:
This is normal and expected. This is only something you see in
a debugger, and is covered in the FAQ. Please just "continue".
Kurt
On Sun, May 07, 2017 at 02:48:26PM +0200, Bernhard Schmidt wrote:
> On 04.05.2017 22:47, Kurt Roeckx wrote:
>
> Hi Kurt,
>
> >>> I was checking 1:4.2.8p10+dfsg-1 that should have fixed this.
> >>
> >> No, 1:4.2.8p10+dfsg-1+exp1 (in experimental) shou
gt; > pool 2.debian.pool.ntp.org iburst
> > pool 3.debian.pool.ntp.org iburst
> >
> > # grep pool /usr/sbin/ntpdate-debian
> >
>
> Kurt, this is the only change in experimental I would consider to fix
> for Stretch, especially since it has been fixed once and got lost
> somewhere. What do you think?
And maybe in jessie too.
Kurt
't see those lines:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA256
They're not part of the signed message. It really shouldn't be
showing that to me.
If I set crypt_use_gpgme=no those lines go away.
I'm really using 1.7.2-1, but I assume it has that behaviour since
1.7.0-2 based on the NEWS file.
Kurt
On Thu, Apr 27, 2017 at 09:25:33PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-04-27 18:18:50 [+0200], Kurt Roeckx wrote:
> >
> > Yes, so perl-base should be find for c_rehash and CA.pl, but tsget
> > requires libwww-curl-perl and we already don't depend on it.
>
On Thu, Apr 27, 2017 at 02:00:47PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-04-23 20:31:35 [+0200], Kurt Roeckx wrote:
> > On Sun, Apr 23, 2017 at 09:12:39AM +, Jonathon Delgado wrote:
> > > So does this require anything from the perl package? I've never had
> &g
Package: ca-certificates
Severity: wishlist
Hi,
Could you switch from calling the c_rehash perl script to the
"openssl rehash"?
I would like to remove c_rehash in the future.
Kurt
, but has any
> such scenario been identified?
We just have to figure out if perl-base is enough or not. I've
asked about this.
Kurt
package. This is only necessary for some
| packages that are included in the base system.
|
| Note that this flag may cause no dependency on
| perl-base to be generated at all. perl-base is Essential, so its
| dependency can be left out, unless a versioned dependency is
| needed.
Kurt
On Thu, Apr 13, 2017 at 09:45:59AM -0700, Tianon Gravi wrote:
> On 13 April 2017 at 09:44, Kurt Roeckx <k...@roeckx.be> wrote:
> > One of the important binaries in c_rehash which is a perl script.
>
> Ahh, and that's used by ca-certificates? :(
Yes.
Kurt
gt; necessary. Would it be acceptable to downgrade that Depends to
> Recommends instead? That would ensure that it's installed on most
> folks' systems, while still allowing people who don't require it to
> exclude it. :)
One of the important binaries in c_rehash which is a perl script.
Kurt
On Sun, Apr 09, 2017 at 02:53:17PM +0200, Julian Andres Klode wrote:
> Control: tag -1 wontfix
>
> On Sun, Apr 09, 2017 at 01:52:03PM +0200, Kurt Roeckx wrote:
> > Package: apt-transport-https
> > Severity: wishlist
> >
> > Hi,
> >
> >
Package: apt-transport-https
Severity: wishlist
Hi,
Can you add http/2 support?
Kurt
On Mon, Apr 03, 2017 at 11:22:19PM +0200, Bernhard Schmidt wrote:
> On Mon, Apr 03, 2017 at 11:15:35PM +0200, Kurt Roeckx wrote:
>
> HI,
>
> > > I tried to reproduce this with current Jessie and the future Stretch
> > > release. As far as I can tell ntp ha
ring DNS for 0.debian.pool.ntp.org 1
> ntpd_initres[...]: host name not found: 0.debian.pool.ntp.org
>
> as soon as DNS and/or network connectivity is available again (a couple
> of minutes later) it logs
>
> ntpd_initres[...]: DNS 0.debian.pool.ntp.org -> IP
>
> and starts using this server.
As far as I know, this only works with the "pool" command, not
with any of the server commands.
Kurt
an empty line before the boundary
marker. I have no idea if that's correct or not. I know I can
verify that signature using mutt, but maybe mutt has some
workaround for it. The mail in question was generated by
evolution.
Kurt
ta instead:
/usr/share/zoneinfo/leap-seconds.list
I also don't trust that script, looking at:
# Where to put temporary copy before it's validated
my $TMPFILE="/tmp/leap-seconds.$$.tmp";
Kurt
-check.patch
-- Kurt Roeckx <k...@roeckx.be> Wed, 22 Mar 2017 21:53:40 +0100
The upstream changes are:
(4.2.8p10)
* [Sec 3389] NTP-01-016: Denial of Service via Malformed Config
(Pentest report 01.2017) <perlin...@ntp.org>
* [Sec 3388] NTP-01-014: Buffer Overflow in DPTS Clock
(Pentest re
On Sat, Mar 18, 2017 at 04:55:51PM +1100, Craig Small wrote:
> Hi Kurt,
> I have applied your patch, it looks like pretty minor API stuff but
> thanks for hunting it all down. I needed to mess around with the
> configure scripts so they found the new calls.
>
> One thing
On Tue, Feb 28, 2017 at 10:02:04AM +0100, Daniel Pocock wrote:
>
> Discussed on debian-devel[1]
As also explain there, the only solution I find acceptable is for
ntpdate-debian to call hwclock.
Kurt
On Thu, Feb 23, 2017 at 01:33:09PM +0100, Bernhard Schmidt wrote:
>
> Will check what could be causing this.
That has been fixed in an NMU, see #851803
Kurt
On Wed, Feb 22, 2017 at 11:21:57PM +0100, Alberto Garcia wrote:
> On Wed, Feb 22, 2017 at 10:59:08PM +0100, Kurt Roeckx wrote:
>
> > > I don't know, I think I would understand you better if I had a
> > > list of specific problems that make this software unsuitable for
&
On Wed, Feb 22, 2017 at 01:56:31PM +0100, Alberto Garcia wrote:
> On Mon, Feb 20, 2017 at 06:52:58PM +0100, Kurt Roeckx wrote:
>
> > It's just that each time I mention I'm using this, people tell me
> > taht it's experimental, and probably a bug in purple-matrix. But
> >
On Tue, Feb 21, 2017 at 02:10:09PM -0500, Peter Eisentraut wrote:
> On 2/19/17 07:01, Kurt Roeckx wrote:
> >>> I could really use some help with the ntp (network time protocol)
> >>> package. There have been various bugs filed, and I didn't have the
> >>>
On Mon, Feb 20, 2017 at 11:21:50AM +0100, Alberto Garcia wrote:
> On Mon, Feb 20, 2017 at 09:33:55AM +0100, Kurt Roeckx wrote:
>
> > > Could you be a bit more specific about the problems? In my
> > > experience it disconnects (infrequently) and it lacks some
> &
On Mon, Feb 20, 2017 at 08:57:55AM +0100, Alberto Garcia wrote:
> On Mon, Feb 20, 2017 at 12:12:35AM +0100, Kurt Roeckx wrote:
>
> > I think this version shouldn't be shipped with the next
> > release. Like the description says, it's "somewhat alpha".
> >
>
Package: purple-matrix
Version: 0.0.0+git20170105-1
Severity: serious
Hi,
I think this version shouldn't be shipped with the next
release. Like the description says, it's "somewhat alpha".
It works some times, but then stops working, it crashes,
and so on.
Kurt
On Sun, Feb 19, 2017 at 07:33:20AM +0100, Cyril Brulebois wrote:
> Kurt Roeckx <k...@roeckx.be> (2017-02-18):
> > On Sat, Feb 18, 2017 at 06:16:28PM +0100, Cyril Brulebois wrote:
> > > How soon do you want to see this package in testing? Given I've just
> > > fi
On Fri, Feb 17, 2017 at 08:56:40AM +0100, Bernhard Schmidt wrote:
> On Thu, Feb 16, 2017 at 11:48:49PM +0100, Kurt Roeckx wrote:
>
> Hi Kurt,
>
> > I could really use some help with the ntp (network time protocol)
> > package. There have been various bugs filed, and I
On Sat, Feb 18, 2017 at 06:16:28PM +0100, Cyril Brulebois wrote:
> Hi,
>
> Niels Thykier <ni...@thykier.net> (2017-02-18):
> > Kurt Roeckx:
> > > Package: release.debian.org
> > > User: release.debian@packages.debian.org
> > > Usertags
-2017-3733
- Remove patches that are applied upstream.
-- Kurt Roeckx <k...@roeckx.be> Thu, 16 Feb 2017 18:57:58 +0100
I've attached the full debdiff between the version in testing and
unstable.
Kurt
diff -Nru openssl-1.1.0d/apps/openssl.c openssl-1.1.0e/apps/openssl.c
--- openssl-1.1.0
the past few years.
Kurt
On Sat, Jan 28, 2017 at 06:07:02PM +0100, gregor herrmann wrote:
> On Sat, 28 Jan 2017 16:35:44 +0100, Kurt Roeckx wrote:
>
> > On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote:
> > > Control: forwarded -1
> > > https://rt.cpan.org/Public/Bug/Displa
On Sat, Jan 28, 2017 at 04:02:02PM +0100, gregor herrmann wrote:
> Control: tag -1 + confirmed
> Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=120006
I've just filed:
https://rt.cpan.org/Public/Bug/Display.html?id=120006
Kurt
On Sat, Jan 28, 2017 at 12:59:43PM +, Daniel Silverstone wrote:
> Control: tag -1 pending
>
> Hi,
>
> I've uploaded the patch previously sent into DELAYED/5
>
> Let me know if this should be expedited.
Just upload it to unstable.
Kurt
an IP address has
> been assigned. This part handles the IPv4 case only since I don't have an
> IPv6 network to test with.
I don't think we should have a while loop in there, or at least
time out after some time.
But we really shouldn't get called if it's not up in the first place.
And calling us with "--all" doesn't make sense at all.
Kurt
s, so please switch
> build-deps to libssl1.0-dev for stretch.
Upstream has actually added a patch for this already in the stable
branch as far as I know, so I expect this to actually have been
fixed in 9.10.4-P5.
That being set, it's not using libssl, so either solution is fine
for me.
Kurt
5193#10) calling link_a.gnu
> > instead of the link_o.gnu target, which tries to link a static library
> > composed of PIE objects into a shared library, which makes it fail.
>
> so is there anything we need to do on the openssl side?
Figure out why it uses link_a instead of link_o, and maybe fix it?
Kurt
On Sat, Dec 24, 2016 at 02:56:53PM +0100, Arnaud Quette wrote:
> Hi Kurt,
>
> are you still facing this issue?
> As far as I recall, I've tested 5S not long ago (Jessie + NUT 2.7.4), and
> everything was fine...
As far as I know, it works sometimes. It ussually works when
they'
On Tue, Dec 20, 2016 at 05:33:12PM +0100, Daniel Pocock wrote:
>
>
> On 19/12/16 23:05, Kurt Roeckx wrote:
>
> >
> > You should use SSL_COMP_free_compression_methods() so that we can
> > put the internal pointer to NULL.
> >
>
> Thanks for sug
me the impression that exploding here is what should be
> > expected and libssl is the victim here.
> >
>
> Thanks for taking the time to look at this.
>
> Is there an example of how this cleanup should be done, or is there a
> specific line of code there that you believe is out of place?
>
> If it is definitely not an openssl issue then the bug can be moved back
> to src:resiprocate
You should use SSL_COMP_free_compression_methods() so that we can
put the internal pointer to NULL.
Kurt
On Sun, Dec 11, 2016 at 08:13:08PM +0100, Joerg Dorchain wrote:
> On Sun, Dec 11, 2016 at 12:57:06PM +0100, Kurt Roeckx wrote:
> > >
> > > > Most reproduceable way I found by now is the DANE validator at
> > > > https://dane.sys4.de/, which leave a log entry e
shake with "ca md too weak".
>
> That is probably because the -7 package got built against openssl 1.1
> while -6 was still at openssl 1.0.
>
> Cc:ing Kurt (the openssl maintainer), maybe he has some hints.
>
> > Most reproduceable way I found by now is the DANE va
On Wed, Nov 30, 2016 at 11:43:13PM +0100, Sebastian Andrzej Siewior wrote:
> On 2016-11-30 21:22:38 [+], Thorsten Glaser wrote:
> > Kurt Roeckx dixit:
> >
> > >But the errors I've always been seeing is a segfault during the
> > >tests, and
o happen. So I
rewrote the openssl part (partially?) to avoid it.
Kurt
diff --git a/libfreerdp/crypto/crypto.c b/libfreerdp/crypto/crypto.c
index 85a28b8..8777ab8 100644
--- a/libfreerdp/crypto/crypto.c
+++ b/libfreerdp/crypto/crypto.c
@@ -98,7 +98,7 @@ static int crypto_rsa_common(const BYTE* inp
On Wed, Nov 30, 2016 at 07:55:55PM +, Thorsten Glaser wrote:
> Kurt Roeckx dixit:
>
> >> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t.
> >
> >But both are actually in installed state now?
>
> Yes because I built it in a chroot in which I do
n m68k backend and this differs from the one implemented in
> the Debian patch. My diff ignores m68k_backend.diff, which is most
> likely not what you want.
I think it should be removed. I've already asked the submitter of
the patch in the upstream version to look at our patch to see if
something else in there is useful, but I didn't get any reply.
Kurt
On Wed, Nov 30, 2016 at 12:07:44PM +, Thorsten Glaser wrote:
> Kurt Roeckx dixit:
>
> >So can someone explain what needs to be fixed in openssl? The
> >order of the CFLAGS needs to be changed?
>
> Unfortunately, I have no idea; 1.1 builds, 1.0 doesn’t.
But both a
so…
> >
> > >So, I think I'll reassign this to openssl1.0, if no other feedback
> >
> > … this is probably legit. But I would *still* like to raise
> > another point.
>
> Ok, thanks, doing so now.
So can someone explain what needs to be fixed in openssl? The
order of the CFLAGS needs to be changed?
Kurt
On Tue, Nov 29, 2016 at 12:56:39PM +0200, Christos Trochalakis wrote:
> Hello Piotr,
>
> I am not really familiar with EC, and before digging deeper I am CCing
> Kurt, one of the OpenSSL maintainers, who can shed some light into the
> issue.
>
> On Mon, Nov 28, 2016 at 12
ckages that fail to build that
build-depend on libssl-dev, even if they breakage isn't caused by
openssl.
You can argue about it either way, it's not important for me.
Kurt
On Fri, Nov 25, 2016 at 10:56:39AM +0100, Philipp Kern wrote:
> On Sun, Oct 30, 2016 at 10:40:42PM +0100, Kurt Roeckx wrote:
> > On Sun, Oct 30, 2016 at 11:35:23PM +0200, Adrian Bunk wrote:
> > > I am raising this to RC severity since 1.0.2 will likely still be
> &
On Mon, Nov 21, 2016 at 04:18:44PM -0800, Tianon Gravi wrote:
> severity 842806 important
> thanks
>
> On 21 November 2016 at 00:18, Kurt Roeckx <k...@roeckx.be> wrote:
> > It's not installed.
>
> So, does installing "cgroupfs-mount" (and making sure
On Sun, Nov 20, 2016 at 07:10:43PM -0800, Tianon Gravi wrote:
> On 2 November 2016 at 00:25, Kurt Roeckx <k...@roeckx.be> wrote:
> > I'm guessing this is something systemd sets up, but that I might
> > need to manually set up if not using it?
>
> Ah yeah, sounds
On Fri, Nov 18, 2016 at 08:05:15PM +0100, Kurt Roeckx wrote:
> On Fri, Nov 18, 2016 at 12:59:57PM +0100, Thorsten Glaser wrote:
> > Breakpoint 1, OPENSSL_atexit (handler=handler@entry=0xf6745c50
> > ) at crypto/init.c:604
> > 604 {
> >
> > There is our 0xf6
dso = DSO_dsobyaddr(handlersym.sym, DSO_FLAG_NO_UNLOAD_ON_FREE);
DSO_free(dso);
}
Kurt
On Wed, Nov 16, 2016 at 11:05:13PM +0100, Stefan Fritsch wrote:
> Hi,
>
> [I have trimmed the cc list a bit]
>
> On Wednesday, 16 November 2016 20:36:49 CET Kurt Roeckx wrote:
> > On Mon, Nov 14, 2016 at 03:06:44PM -0800, Russ Allbery wrote:
> > > Stefan Fr
501 - 600 of 6713 matches
Mail list logo
