xlock clarification....

hedleyCS.BRIS.AC.UK

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: J.R.Valverde: "Re: Smashing the Stack: prevention?"
• Previous message: Tim Newsham: "Re: Smashing the Stack: prevention?"

Just to clarify the xlock problem for people (as I've received email
from several people who aren't sure if they're vulnerable or not). The
length of the parameter has to exceed 1024 bytes (as the buffer being
overflowed is 1024 characters). e.g. try: xlock -name xxxxx<insert 1000+x's>

Regards,

David
--
 David Hedley (hedleycs.bris.ac.uk)
 finger hedleycs.bris.ac.uk for PGP key
 Computer Graphics Group | University of Bristol | UK

• Next message: J.R.Valverde: "Re: Smashing the Stack: prevention?"
• Previous message: Tim Newsham: "Re: Smashing the Stack: prevention?"