[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Mu [was: How worse is the Shellshock bash bug than Heartbleed?]

To: Georgi Guninski <[email protected]>, [email protected]
Subject: Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
From: [email protected] (coderman)
Date: Wed, 1 Oct 2014 14:08:56 -0700
Cc: [email protected]
In-reply-to: <[email protected]$>
References: <CAJVRA1Q1CVpS-QoWvV7QtN7OqPBa_ZdeJ4yGC=RRHN3DyM4E-g@mail.gmail.com> <[email protected]$> <CAJVRA1QqeRKPqNdG4eNr3QmmmmCf98+uKUyBVxkfOp4tFWdngw@mail.gmail.com> <[email protected]$>

On 10/1/14, Georgi Guninski <[email protected]> wrote:
>> <codermange> rant'eth: ....
>> to reiterate, in case anyone missed it: exposing a shell to untrusted
>> inputs is insanity. this is true even if you manage to make your
>> environment variable sanitization apparently robust.
>>
>
> OK :) Tell this to djb, qmail local delivery was allegedly affected ;)


even the best of us are only human.  :/

reason #75,312 that email must die in a fire!
 (i'd also note there is no httpS://cr.yp.to/ ...)


best regards,

References:
- Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
  - From: [email protected] (Georgi Guninski)
- Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
  - From: [email protected] (coderman)
- Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
  - From: [email protected] (Georgi Guninski)

Prev by Date: BitNation
Next by Date: Fwd: [tor-talk] Tor in the media - request for unsung positive narratives
Previous by thread: Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
Next by thread: Mu [was: How worse is the Shellshock bash bug than Heartbleed?]
Index(es):
- Date
- Thread