background preloader

Hacking

Facebook Twitter

VLC Current Track to Google Talk Status [VLC2GTalk v1.0 BETA] I made one small script that checks VLC for the current track and sends this track name to Google Talk so that your google talk status gets updated with the current VLC track. This is similar to plugins available for Google Talk with ITunes, Winamp and so on. I created this small script because i use VLC, im a music lover, so i listen to songs in 200% volume, which is available in VLC only, so i use VLC and then thought of developing a small script for posting the current track to Google Talk Screenshot: Here is the download link: (514 KB) And for coders, here is the source code: (Its an AutoHotKey code) I just checked it and it works, if you find any bugs please post it here, so that we can try to resolve them. Anyways, if anyone wants to try developing the same. Chromium Blog. Hovav Shacham: Return-Oriented Programming. Joint work with By Erik Buchanan, Ryan Roemer, and Stefan Savage.

Given at Black Hat USA 2008 Briefings. Aug. 2008. Abstract We describe return-oriented programming, a generalization of return-into-libc that allows an attacker to undertake arbitrary, Turing-complete computation without injecting code. New computations are constructed by linking together code snippets that end with a “ret” instruction. The ret instructions allow an attacker who controls the stack to chain instruction sequences together. W^X and DEP, along with many other security systems, make the assumption that preventing the introduction of malicious code is sufficient to prevent the introduction of malcious computation. On the x86 one can obtain useful instruction sequences by jumping into the middle of intended instructions, but return-oriented programming is possible even on RISC platforms that are very different from the x86.

Material talk slides at Black Hat (PDF). See Also. Www.suse.de/~krahmer/no-nx.pdf. Anatomy of a hack: 6 separate bugs needed to bring down Google browser (Updated) An exploit that fetched a teenage hacker a $60,000 bounty targeted six different security bugs to break out of the security sandbox fortifying Google's Chrome browser. The extreme lengths taken in March by a hacker identified only as Pinkie Pie underscore the difficulty of piercing this safety perimeter.

Google developers have erected their sandbox to separate Web content from sensitive operating-system functions, such as the ability to read and write files to a hard drive. Such sandboxes are designed to minimize the damage that can be done when attackers identify and exploit buffer overflows and other types of software bugs that inevitably find their way into complex bodies of code.

Pinkie Pie's attack came during Pwnium, a contest that awarded $60,000 prizes to hackers who successfully broke out of the protective barrier by exploiting only vulnerabilities residing in code that is native to the Google browser. The teenager was one of only two contestants to win the top prize. 59.120.154.62.