phs2501

20 ms·

1. 181.▲
   by phs2501 12y ago

   No, bash interprets as functions ALL environment variables that begin with '() {' on startup. If you have an unpatched bash it will also excute any trailing commands after the function definition. You don't need to manually
2. 182.▲
   by phs2501 12y ago

   Not true if the perl script calls out to bash (i.e. via system), as it doesn't sanitize the environment: $ env x='() { :;}; echo vulnerable' perl -T -e "\$ENV{PATH} = '/bin'; system('ls | cat&#x
3. 183.▲
   Introducing Tweet-a-Program(blog.wolfram.com)

   158 points by phs2501 12y ago|54 comments
4. 184.▲
   by phs2501 12y ago

   That'd be a syntactic ambiguity (in C-type languages) between "a * * b" being a to the power of b (i.e. "(a) * * (b)") or "a * * b" being a times the dereferencing of the pointer b (i.e. "(a) * (*b)&q
5. 185.▲
   by phs2501 12y ago

   What you're seeing is that Chrome is using the (terrible) old Windows GDI ClearType font rendering, whereas Firefox is using the (newer, less terrible) DirectWrite font rendering. This can be enabled in Chrome by visiting chrome:&#x2F