lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <53AF0C31.7070509@privacyrequired.com> Date: Sat, 28 Jun 2014 11:40:49 -0700 From: * <turmoil@...vacyrequired.com> To: fulldisclosure@...lists.org Subject: Re: [FD] Back To The Future: Unix Wildcards Gone Wild On 06/28/2014 03:26 AM, steel-wing@....net wrote: > Unfortunately, this analysis is just as flawed as defencecode's. > Programs like 'rm' are even less "to blame" for this than the shell. > As to the proposed solution: > What you are suggesting is to have rm attempt to match every > option passed to it against every file single before said file > is to be removed. Correct? I'm mostly siding with the others on the list saying this is both very old, and mostly a non-issue, but the problem shown isn't in called programs, like rm, but of the shell. If there ever is to be a fix for this, it'd probably be to have an option of the shell to warn the user that there are strings in any expanded variables that may be interpreted as -arguments. _______________________________________________ Sent through the Full Disclosure mailing list http://nmap.org/mailman/listinfo/fulldisclosure Web Archives & RSS: http://seclists.org/fulldisclosure/
Powered by blists - more mailing lists