<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
   <channel>
      <title>halfdog.net RSS feed</title>
      <link>https://www.halfdog.net/</link>
      <description>Halfdog.net related news channel: an automated way to get new information independent from third parties. The main topics are application and operating system security, secure programming, vulnerability analysis and exploitation, security best practices.</description>
      <language>en-us</language>
      <pubDate>Fri, 01 Feb 2019 00:00:00 +0000</pubDate>
      <lastBuildDate>Sat, 02 Feb 2019 00:00:00 +0000</lastBuildDate>
      <ttl>60</ttl>
      <category>IT Security</category>
      <copyright>Copyright 2019 me at halfdog.net</copyright>
      <generator>Manually</generator>
      <managingEditor>me at halfdog.net @ keep-validator-happy</managingEditor>
      <webMaster>admin at halfdog.net @ keep-validator-happy</webMaster>
      <atom:link href="https://www.halfdog.net/rss.xml" rel="self" type="application/rss+xml" />

      <item>
         <title>Use data from any SSL client certificate field for Exim
authentication process</title>
         <link>https://www.halfdog.net/Blog/#Log20190131-EximSslClientAuthWithNondefaultCertificateFields</link>
         <description>Exim may use some fields from
SSL client certificates in the authentication procedure, e.g.
mailAddress, but others are not supported. The x500UniqueIdentifier
field is not understood, which could be used by Dovecot to force
the login user name to be the one from the SSL certificate. To
use x500UniqueIdentifier in Exim and Dovecot this QUITE HACKY
workaround can be used. Read more at
https://www.halfdog.net/Blog/2019/EximSslClientAuthWithNondefaultCertificateFields/ ...
</description>
         <pubDate>Sat, 02 Feb 2019 00:00:00 +0000</pubDate>
         <guid isPermaLink="false">https://www.halfdog.net/Blog/#Log20190131-EximSslClientAuthWithNondefaultCertificateFields</guid>
      </item>
   </channel>
</rss>
