<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Esoteric-Programming on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/esoteric-programming/</link><description>Recent content in Esoteric-Programming on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Mon, 13 Aug 2012 19:32:00 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/esoteric-programming/index.xml" rel="self" type="application/rss+xml"/><item><title>Brainfuck beware: JavaScript is after you!</title><link>http://karpoke.ignaciocano.com/2012/08/13/brainfuck-beware-javascript-is-after-you/</link><pubDate>Mon, 13 Aug 2012 19:32:00 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2012/08/13/brainfuck-beware-javascript-is-after-you/</guid><description>&lt;blockquote&gt;
&lt;p&gt;I just made a tool to transform any javascript code into an equivalent
sequence of ()[]{}!+ characters. You can try it here, or grab it from
github or npm. Keep on reading if you want to know how it works.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;What do you know about non-alphanumeric XSS?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The other day one of my friends asked me that question on IRC,
pointing me to some articles on sla.ckers.org where they tried to
create some scripts like alert(1) with non-alphanumeric characters.&lt;/p&gt;
&lt;p&gt;As a security researcher and a penetration tester, he insisted that
extending that concept to any javascript source would be really useful
for bypassing IDSs, IPSs and WAFs. So challange accepted!&lt;/p&gt;
&lt;/blockquote&gt;</description></item></channel></rss>