I updated openssl on my system and ran into this bug:
As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is broken.
You need to grab
http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247 and
apply it to the 1.0.1d source to fix it.
Will this patch be applied to the
Jerry je...@seibercom.net wrote:
I updated openssl on my system and ran into this bug:
As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is
broken. You need to grab
http://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=32cc247
and apply it to the 1.0.1d source to fix
On Fri, 8 Feb 2013 21:03:07 + (UTC)
Michael Grimm articulated:
Jerry je...@seibercom.net wrote:
I updated openssl on my system and ran into this bug:
As noted numerous times on the openssl-dev list, OpenSSL 1.0.1d is
broken. You need to grab
Jerry je...@seibercom.net wrote:
Usually I never update any software to a new version until it has been
in use for a while. However, since this was not a major update, but
just a minor letter, I figured how badly could I get burnt.
Hmm, I did follow the advice in my daly security report:
|
Dirk Meyer ha scritto:
Sadly there have been regressions at runtime.
$ ldd binary
What is this binary ? And please post the output of ldd -a.
--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://docs.freebsd.org/cgi/mid.cgi?201001121543.o0CFhqWv076278
What happened? I haven't been able to find any discussion about this
on either freebsd-ports, freebsd-ports-bugs, or freebsd-security.
There doesn't seem to be a PR, either.
Am I just being overly sensitive or does this present a
Hi Trix,
http://docs.freebsd.org/cgi/mid.cgi?201001121543.o0CFhqWv076278
What happened? I haven't been able to find any discussion about this
on either freebsd-ports, freebsd-ports-bugs, or freebsd-security.
There doesn't seem to be a PR, either.
I'm also wondering and waiting for an
On Wednesday 13 Jan 2010 12:00:23 Trix Farrar wrote:
What happened? I haven't been able to find any discussion about this
on either freebsd-ports, freebsd-ports-bugs, or freebsd-security.
There doesn't seem to be a PR, either.
Am I just being overly sensitive or does this present a POLA
On Wednesday 13 Jan 2010 13:34:29 I wrote:
I suspect that there's an update on its way, although that doesn't help
the rest of us using ports in the meantime. For now, I'd personally
recommend to use a date=2010.01.12.15.42.00 definition in your ports
supfile until all of this shakes out.
On Wed, Jan 13, 2010 at 05:26:59AM -0600, Trix Farrar wrote:
What happened?
I got an e-mail from maintainer din...@freebsd.org. There was,
evidently, a breakage introduced when threading library linkage was
removed
(http://docs.freebsd.org/cgi/mid.cgi?201001051213.o05CDu49061700).
This
Trix Farrar ha scritto:
I got an e-mail from maintainer din...@freebsd.org. There was,
evidently, a breakage introduced when threading library linkage was
removed
Nothing is evident here. The port was deprecated because of unfixed
vulnerabilities and worked for most of you.
--
Alex Dupre
I'd like to echo some of the others regarding the recent changes in
security/openssl: since this port is used by a large number of
people, it would be better to announce major changes in advance, and
to test more carefully before committing.
The reverted deprecation leaves me a bit puzzled.
On 1/13/10, b. f. bf1...@googlemail.com wrote:
I note that there are still a few obvious minor flaws after the most
recent commits, including what looks like an unintentional inversion
of the logic surrounding the SSE2 option. I'm attaching a suggested
patch.
In addition to the other
13 matches
Mail list logo
