On 2/25/16 12:20 PM, Stephane Chazelas wrote:
> 2016-02-25 10:48:51 -0500, Chet Ramey:
> [...]
>> Because bash doesn't have floating point arithmetic.
>
> Yes, makes sense. mksh having $EPOCHREALTIME floating point even
> though it doesn't have floating point arithmetic does sound
> weird.
>
> An
Good Morning/Afternoon/Evening,
Is there a set process in place for reporting security vulnerabilities
against bash? If so, what might that process be?
Thank you much!
Regards,
Travis Garrell
On 02/26/2016 07:54 AM, Travis Garrell wrote:
> Good Morning/Afternoon/Evening,
>
> Is there a set process in place for reporting security vulnerabilities
> against bash? If so, what might that process be?
Very few bugs in bash are security vulnerabilities (shellshock being the
obvious exception)
On Fri, Feb 26, 2016 at 8:54 AM, Travis Garrell
wrote:
> Is there a set process in place for reporting security vulnerabilities
> against bash? If so, what might that process be?
Mail the maintainer. See:
https://tiswww.case.edu/php/chet/bash/bashtop.html#Bugs
Encrypt with: https://tiswww.case.ed
On Fri, Feb 26, 2016 at 10:02 AM, Eric Blake wrote:
> Very few bugs in bash are security vulnerabilities (shellshock being the
> obvious exception). Yes, bash has bugs, but in most cases, what people
> think are security bugs in bash are actually poorly-written shell
> functions that crash for th
On 2/26/16 11:13 AM, Dan Douglas wrote:
> On Fri, Feb 26, 2016 at 10:02 AM, Eric Blake wrote:
>> Very few bugs in bash are security vulnerabilities (shellshock being the
>> obvious exception). Yes, bash has bugs, but in most cases, what people
>> think are security bugs in bash are actually poorl
