<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Security on Dimitri Laaraybi</title>
    <link>https://www.dimitrilaaraybi.com/tags/security/</link>
    <description>Recent content in Security on Dimitri Laaraybi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Thu, 17 Aug 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.dimitrilaaraybi.com/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to switch from Moq to NSubstitute after the SponsorLink scandal ?</title>
      <link>https://www.dimitrilaaraybi.com/blog/moqtonsubstitute/</link>
      <pubDate>Thu, 17 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/moqtonsubstitute/</guid>
      <description>&lt;p&gt;Hey devs ! 😁&lt;/p&gt;&#xA;&lt;p&gt;If you are a .NET developer who uses the popular mocking library Moq for your unit tests, you may have heard about the recent controversy that erupted when it was revealed that Moq was secretly collecting and sending user email addresses to a third-party service called SponsorLink. This was done &lt;a href=&#34;https://www.reddit.com/r/dotnet/comments/15ljdcc/does_moq_in_its_latest_version_extract_and_send/&#34;&#xA;    target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&#xA;  without the consent or knowledge of the developers who used Moq&#xA;&lt;/a&gt;, and raised serious privacy and security concerns.&lt;br&gt;&#xA;In this post, I&amp;rsquo;ll try to explain in more details what this scandal is all about and how to switch from Moq to NSubstitute if you see fit, but also how to prevent your projects from those vulnerabilities in a DevSecOps way 😉&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to implement App Service integrated authentication (Easy Auth)</title>
      <link>https://www.dimitrilaaraybi.com/blog/azureadeasyauth/</link>
      <pubDate>Sat, 27 May 2023 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/azureadeasyauth/</guid>
      <description>&lt;p&gt;Authentication is a standard when it comes to manage security and access to your business applications. And Azure provides numerous ways to handle that security layer.  &lt;!-- raw HTML omitted --&gt;&#xA;In this blog post, I&amp;rsquo;m going to talk about integrated authentication for app services (easy auth) in Azure. I&amp;rsquo;ll explain what it is, what are the advantages and disadvantages compared to authentication managed in code, and how to implement it on an app service.   &lt;!-- raw HTML omitted --&gt;&#xA;Let&amp;rsquo;s get started 😄&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
