<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>JavaScript on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/javascript/</link>
    <description>Recent content in JavaScript on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 06 Feb 2020 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/javascript/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>TROOPERS20 Training Teaser: Hacking Node.js &amp; Electron apps, shells, injections and fun!</title>
      <link>https://insinuator.net/2020/02/troopers20-training-teaser-hacking-node.js-electron-apps-shells-injections-and-fun/</link>
      <pubDate>Thu, 06 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2020/02/troopers20-training-teaser-hacking-node.js-electron-apps-shells-injections-and-fun/</guid>
      <description>&lt;p&gt;Did you know that in the ever evolving field of Web and Desktop apps, it turns out these can all now be powered with JavaScript? You read that right: JavaScript is now used to power both web apps (Node.js) as well as Desktop apps (Electron). What could possibly go wrong?&lt;/p&gt;&#xA;&lt;p&gt;So, the burning question is: how does this affect Web and Desktop app security? If you want to find out, come to our training and you will experience this in a 100% hands-on fashion! 🙂&lt;/p&gt;</description>
    </item>
    <item>
      <title>Implementing an Obsolete VPN Protocol on Top of HTTP: Because Why Not?</title>
      <link>https://insinuator.net/2016/05/implementing-an-obsolete-vpn-protocol-on-top-of-http-because-why-not/</link>
      <pubDate>Tue, 31 May 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/05/implementing-an-obsolete-vpn-protocol-on-top-of-http-because-why-not/</guid>
      <description>&lt;p&gt;Recently I’ve started some research on MikroTik’s RouterOS, the operating system that ships with RouterBOARD devices. As I’m running such a device myself, one day I got curious about security vulnerabilities that have been reported on the operating system and the running services as it comes with tons of &lt;a href=&#34;http://wiki.mikrotik.com/wiki/Manual:RouterOS_features&#34;&gt;features&lt;/a&gt;. Searching for known vulnerabilities in RouterOS on Google doesn’t really yield a lot of recent security related stuff. So I thought, there is either a lack of (public) research or maybe it is super secure… 🙂&lt;/p&gt;</description>
    </item>
    <item>
      <title>Some Security Impacts of HTML5 CORS or How to use a Browser as a Proxy</title>
      <link>https://insinuator.net/2013/08/some-security-impacts-of-html5-cors-or-how-to-use-a-browser-as-a-proxy/</link>
      <pubDate>Mon, 26 Aug 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/08/some-security-impacts-of-html5-cors-or-how-to-use-a-browser-as-a-proxy/</guid>
      <description>&lt;p&gt;With HTML 5 the current web development moves from server side generated content and layout to client side generated. Most of the so called &lt;em&gt;HTML5 powered&lt;/em&gt; websites use JavaScript and CSS for generating beautiful looking and responsive user experiences. This ultimately leads to the point were developers want to include or request third-party resources. &lt;em&gt;Un&lt;/em&gt;fortunately all current browsers prevent scripts to request external resources through a security feature called the &lt;em&gt;Same-Origin-Policy&lt;/em&gt;. This policy specifies that client side code could only request resources from the domain being executed from. This means that a script from example.com can not load a resource from google.com via AJAX(XHR/XmlHttpRequest).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
