<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Dagolden on Hashbang.ca</title>
		<link>https://hashbang.ca/tag/dagolden</link>
		<description>Recent content in Dagolden on Hashbang.ca</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Wed, 18 Apr 2012 16:47:00 -0400</lastBuildDate>
		
			<atom:link href="https://hashbang.ca/tag/dagolden/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>SSL security in HTTP::Tiny</title>
				<link>https://hashbang.ca/post/ssl-security-in-httptiny</link>
				<pubDate>Wed, 18 Apr 2012 16:47:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/ssl-security-in-httptiny/</guid>
				<description>&lt;p&gt;I was asked to add SSL support to a client library, while also moving from home-grown manual HTTP code to a proper module. &lt;a href=&#34;https://metacpan.org/module/HTTP::Tiny&#34;&gt;&lt;code&gt;HTTP::Tiny&lt;/code&gt;&lt;/a&gt; was ideal because it is pure-Perl, a core module since 5.14 (so it&amp;rsquo;ll be maintained), and it&amp;rsquo;s just one .pm file, making it easy to ship.&lt;/p&gt;&#xA;&lt;p&gt;An application server that supported SSL was provided for testing purposes, but the SSL certificate didn&amp;rsquo;t match the hostname &amp;ndash; &lt;code&gt;HTTP::Tiny&lt;/code&gt; correctly rejected connections. I needed to be able to control the settings sent to the underlying &lt;code&gt;IO::Socket::SSL&lt;/code&gt; object used for the encrypted connection so I could turn off security features for testing. As I worked on that, David Golden offered invaluable feedback, which greatly improved the design of the features added to &lt;code&gt;HTTP::Tiny&lt;/code&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;As of &lt;a href=&#34;https://metacpan.org/module/HTTP::Tiny#SSL-SUPPORT&#34;&gt;0.018&lt;/a&gt;, &lt;code&gt;HTTP::Tiny&lt;/code&gt; is more configurable, and has a simple interface for &lt;em&gt;easily&lt;/em&gt; making SSL connections more secure.&lt;/strong&gt;&lt;/p&gt;</description>
			</item>
			<item>
				<title>Dist::Zilla::Plugin::Twitter gets an OAuth update</title>
				<link>https://hashbang.ca/post/distzillaplugintwitter-gets-an-oauth-update</link>
				<pubDate>Mon, 02 Apr 2012 15:04:00 -0400</pubDate>
				<guid>https://hashbang.ca/post/distzillaplugintwitter-gets-an-oauth-update/</guid>
				<description>&lt;p&gt;My pluginbundle for &lt;a href=&#34;http://dzil.org&#34;&gt;&lt;code&gt;Dist::Zilla&lt;/code&gt;&lt;/a&gt; includes, among other things, the Twitter plugin so I can brag on Twitter every time I release a module. Mysteriously, it &lt;a href=&#34;https://rt.cpan.org/Public/Bug/Display.html?id=75995&#34;&gt;broke&lt;/a&gt; one day. Looking at the code, I realized that it was sending my username and password to authenticate. I remember being uneasy with that at the time I set it up, but I quickly forgot, and continued along blithely. &lt;a href=&#34;https://en.wikipedia.org/wiki/OAuth&#34;&gt;OAuth&lt;/a&gt; is an authorization standard that allows users to avoid giving their username &amp;amp; password to a potentially-untrusted application. Using OAuth has been requested &lt;a href=&#34;https://rt.cpan.org/Public/Bug/Display.html?id=72918&#34;&gt;since 2011&lt;/a&gt;, and the &lt;code&gt;401 Unauthorized&lt;/code&gt; error I got indicates that now it is mandatory for Twitter.&lt;/p&gt;&#xA;&lt;p&gt;David Golden offered to let me maintain the module, and I&amp;rsquo;m a sucker, so&amp;hellip; :D&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
