<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Crypto &#8211; privacyID3A</title>
	<atom:link href="https://www.privacyidea.org/tag/crypto/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.privacyidea.org</link>
	<description>flexible, Open Source Multi Factor Authentication (2FA)</description>
	<lastBuildDate>Fri, 15 Jan 2016 17:00:06 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.7.5</generator>

<image>
	<url>https://www.privacyidea.org/wp-content/uploads/2016/06/cropped-only-logo-white-background-32x32.png</url>
	<title>Crypto &#8211; privacyID3A</title>
	<link>https://www.privacyidea.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Crypto Considerations</title>
		<link>https://www.privacyidea.org/crypto-considerations/</link>
					<comments>https://www.privacyidea.org/crypto-considerations/#respond</comments>
		
		<dc:creator><![CDATA[Cornelius Kölbel]]></dc:creator>
		<pubDate>Fri, 15 Jan 2016 17:00:06 +0000</pubDate>
				<category><![CDATA[documentation]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Crypto]]></category>
		<guid isPermaLink="false">https://www.privacyidea.org/?p=846</guid>

					<description><![CDATA[Today I added the crypto considerations to the FAQ section of the privacyIDEA documentation. Users who might want to use privacyIDEA will wonder how crypto is handled. So this makes it easier for them to get a first impression without having to study the source code. In fact this is also a good review for the project [&#8230;]]]></description>
										<content:encoded><![CDATA[<p><a href="https://www.privacyidea.org/wp-content/uploads/2016/01/cryptography-1091254_640.jpg" rel="attachment wp-att-848"><img decoding="async" class="size-medium wp-image-848 alignleft" src="https://www.privacyidea.org/wp-content/uploads/2016/01/cryptography-1091254_640-300x212.jpg" alt="cryptography-1091254_640" width="300" height="212" srcset="https://www.privacyidea.org/wp-content/uploads/2016/01/cryptography-1091254_640-300x212.jpg 300w, https://www.privacyidea.org/wp-content/uploads/2016/01/cryptography-1091254_640.jpg 640w" sizes="(max-width: 300px) 100vw, 300px" /></a>Today I added the <a href="http://privacyidea.readthedocs.org/en/latest/faq/crypto-considerations.html" target="_blank">crypto considerations to the FAQ section of the privacyIDEA documentation</a>.</p>
<p>Users who might want to use privacyIDEA will wonder how crypto is handled. So this makes it easier for them to get a first impression without having to study the source code.</p>
<p>In fact this is also a good review for the project itself, too. At several places we still use hard coded SHA256. With the hashing of the OTP Pins and the signing of the Audit data.</p>
<p>But having this crypto paper at hand, we know, which places we need to touch in only a few years!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.privacyidea.org/crypto-considerations/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
