<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Infosec on galvanist</title>
    <link>/tags/infosec/</link>
    <description>Recent content in Infosec on galvanist</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 13 May 2020 22:13:52 +0000</lastBuildDate>
    <atom:link href="/tags/infosec/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Django SECRET_KEY generation</title>
      <link>/posts/2020-05-14-django_secret_key_generation/</link>
      <pubDate>Wed, 13 May 2020 22:13:52 +0000</pubDate>
      <guid>/posts/2020-05-14-django_secret_key_generation/</guid>
      <description>&lt;h1 id=&#34;generate-django-secret_keys-on-the-command-line-using-this-one-liner-django-not-required&#34;&gt;Generate django &lt;code&gt;SECRET_KEY&lt;/code&gt;s on the command line using this &amp;ldquo;one-liner&amp;rdquo; (django not required)&lt;/h1&gt;&#xA;&lt;h3 id=&#34;background&#34;&gt;Background&lt;/h3&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://www.djangoproject.com/&#34;&gt;Django&lt;/a&gt; is a Python web framework with a lot of nice features including an exceptional ORM and &lt;a href=&#34;https://docs.djangoproject.com&#34;&gt;high quality documentation&lt;/a&gt;. Most of my experience with django has been deploying and debugging other people&amp;rsquo;s projects - during the course of which I often want to regenerate the &lt;code&gt;SECRET_KEY&lt;/code&gt; that underpins most of the security of every deployment.&lt;/p&gt;&#xA;&lt;p&gt;The &lt;a href=&#34;https://docs.djangoproject.com/en/3.0/ref/settings/#std:setting-SECRET_KEY&#34;&gt;django settings docs&lt;/a&gt; describe the &lt;code&gt;SECRET_KEY&lt;/code&gt;:&lt;/p&gt;</description>
    </item>
    <item>
      <title>macOS JavaScript for Automation (JXA) Notes</title>
      <link>/posts/2020-03-28-jxa_notes/</link>
      <pubDate>Sat, 28 Mar 2020 18:28:48 +0100</pubDate>
      <guid>/posts/2020-03-28-jxa_notes/</guid>
      <description>&lt;h1 id=&#34;overview&#34;&gt;Overview&lt;/h1&gt;&#xA;&lt;p&gt;There is a macOS feature called the &lt;a href=&#34;https://en.wikipedia.org/wiki/AppleScript#Open_Scripting_Architecture&#34;&gt;Open Scripting Architecture&lt;/a&gt; (OSA) which provides an infrastructure for intercommunication and automation of macOS software. One of the officially supported OSA languages is JavaScript and its use in this context is called &amp;ldquo;JavaScript for Automation&amp;rdquo; which is often abbreviated to &amp;ldquo;&lt;strong&gt;JXA&lt;/strong&gt;&amp;rdquo;.&lt;/p&gt;&#xA;&lt;p&gt;The idea is that instead of using &lt;a href=&#34;https://en.wikipedia.org/wiki/AppleScript&#34;&gt;AppleScript&lt;/a&gt;, you can program &amp;amp; automate macOS using a more modern language like &lt;a href=&#34;https://en.wikipedia.org/wiki/JavaScript&#34;&gt;JavaScript&lt;/a&gt;. This gives the programmer access to the enormous ecosystem of javascript libraries and tools in addition to all the modern optimizations and language features of ES6-ish JavaScript. JXA also provides access to a built-in Objective-C bridge that enables access to the file system and the ability to call into the Cocoa frameworks and plain C functions. JXA can basically do anything native code can. It&amp;rsquo;s a bit like &lt;a href=&#34;https://en.wikipedia.org/wiki/Node.js&#34;&gt;node&lt;/a&gt; without needing to install node.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Security Resources for Your New Website</title>
      <link>/posts/2020-03-11-security-resources/</link>
      <pubDate>Wed, 11 Mar 2020 23:32:43 +0100</pubDate>
      <guid>/posts/2020-03-11-security-resources/</guid>
      <description>&lt;p&gt;Establishing a reasonable amount of security for a website is a non-trivial unending job. Here are some notes and resources that I find helpful.&lt;/p&gt;&#xA;&lt;h1 id=&#34;web-server-config&#34;&gt;Web Server Config&lt;/h1&gt;&#xA;&lt;h2 id=&#34;start-with-tls&#34;&gt;Start with TLS&lt;/h2&gt;&#xA;&lt;p&gt;All public-facing websites need to be protected by &lt;a href=&#34;https://en.wikipedia.org/wiki/Transport_Layer_Security&#34;&gt;Transport Layer Security&lt;/a&gt; (TLS). TLS is a technology which allows web traffic to be encrypted and this encryption helps to protect the privacy and security of the users of a site.&lt;/p&gt;&#xA;&lt;p&gt;Deploying a site with TLS can be accomplished in a free and automated fashion. Services like &lt;a href=&#34;https://en.wikipedia.org/wiki/Let&#39;s_Encrypt&#34;&gt;Let&amp;rsquo;s Encrypt&lt;/a&gt; and the issuance features of large cloud providers (for example &lt;a href=&#34;https://aws.amazon.com/certificate-manager/&#34;&gt;AWS Certificate Manager&lt;/a&gt;) encourage more secure defaults and automatic management. For more information, check out the &lt;a href=&#34;https://letsencrypt.org/getting-started/&#34;&gt;Let&amp;rsquo;s Encrypt Getting Started Guide&lt;/a&gt; or your hosting provider&amp;rsquo;s documentation.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
