On 04/25/2014 02:47 AM, Guus Snijders wrote:
> Probably a stupid question, but you did restart the affected daemons (or
> system) after the update?
> Otherwise, they'll be using the old lib.
>
> mvg, Guus
No question too stupid -- I had not. (I knew better...)
Thanks, Sorry for the noise.
--
D
I was testing my boxes after updating to openssl 1.0.1.g-1 with heartbleed.c
and I am still able to grab and decrypt ssl packets.
Most probably you didn't restart the services that link to openssl.
lsof +c 0 | grep -w DEL | awk '1 { print $1 ": " $NF }' | grep libssl |
sort -u
https://mai
I tested my server after the update and found no problems...
On Apr 25, 2014 10:41 AM, "David C. Rankin"
wrote:
> Guys,
>
> I was testing my boxes after updating to openssl 1.0.1.g-1 with
> heartbleed.c
> and I am still able to grab and decrypt ssl packets. The openssl security
> note
> says 1.
Op 25 apr. 2014 09:41 schreef "David C. Rankin" <
drankina...@suddenlinkmail.com> het volgende:
>
> Guys,
>
> I was testing my boxes after updating to openssl 1.0.1.g-1 with
heartbleed.c
> and I am still able to grab and decrypt ssl packets. The openssl security
note
> says 1.0.1.g is not effecte
Guys,
I was testing my boxes after updating to openssl 1.0.1.g-1 with heartbleed.c
and I am still able to grab and decrypt ssl packets. The openssl security note
says 1.0.1.g is not effected by the bug, but I can still get a 64k chuck of data
back from my server using the heartbleed.c test. (if
5 matches
Mail list logo