<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backend on Dean’s blog</title><link>https://blog.thomasdurand.fr/tags/backend/</link><description>Recent content in Backend on Dean’s blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 14 Dec 2023 20:00:00 +0100</lastBuildDate><atom:link href="https://blog.thomasdurand.fr/tags/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>Don’t ship API keys!</title><link>https://blog.thomasdurand.fr/story/2023-12-14-dont-ship-api-keys/</link><pubDate>Thu, 14 Dec 2023 20:00:00 +0100</pubDate><guid>https://blog.thomasdurand.fr/story/2023-12-14-dont-ship-api-keys/</guid><description>&lt;p&gt;Not so long ago, I read about &lt;a href="https://augmentedcode.io/2023/11/27/using-on-demand-resources-for-securely-storing-api-keys-in-ios-apps/" target="_blank" rel="noopener noreferrer"&gt;this article&lt;/a&gt; from &lt;a href="https://mastodon.social/@toomasvahter" target="_blank" rel="noopener noreferrer"&gt;Thomas Vahter&lt;/a&gt; suggesting the distribution of API keys through on-demand resources. Although this approach is appealing, I suggest a different approach: avoid shipping your API keys at all costs!&lt;/p&gt;</description></item></channel></rss>