<?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 Maarten on IT</title><link>https://maarten.mulders.it/categories/security/</link><description>Recent content in Security on Maarten on IT</description><generator>Hugo</generator><language>en-us</language><copyright>&amp;copy; 2013 - 2026 Maarten Mulders</copyright><lastBuildDate>Tue, 07 Jan 2025 12:55:20 +0100</lastBuildDate><atom:link href="https://maarten.mulders.it/categories/security/index.xml" rel="self" type="application/rss+xml"/><item><title>Authenticate Jakarta EE apps with Google using OpenID Connect</title><link>https://maarten.mulders.it/2024/08/authenticate-jakarta-ee-apps-with-google-using-openid-connect/</link><pubDate>Tue, 20 Aug 2024 10:02:00 +0200</pubDate><guid>https://maarten.mulders.it/2024/08/authenticate-jakarta-ee-apps-with-google-using-openid-connect/</guid><description>&lt;p&gt;In one of my pet projects, I&amp;rsquo;m writing a Jakarta EE web application where I want users to authenticate using Google.
Easy, you would say, as Jakarta EE 10 includes Jakarta Security 3.0, which has support for OpenID Connect authentication.
Took me a bit more time to figure out how to get it working, and to save you from having to do that, here&amp;rsquo;s what I found.&lt;/p&gt;</description></item><item><title>Securing Apache HTTPD with Microsoft Active Directory</title><link>https://maarten.mulders.it/2019/03/securing-apache-httpd-with-microsoft-active-directory/</link><pubDate>Tue, 26 Mar 2019 08:07:13 +0200</pubDate><guid>https://maarten.mulders.it/2019/03/securing-apache-httpd-with-microsoft-active-directory/</guid><description>&lt;p&gt;Recently, I was building a website with documentation for one of the projects I&amp;rsquo;m involved with.
I wanted to protect access to that website to a specific set of people inside my company.
Here&amp;rsquo;s how I did it.&lt;/p&gt;</description></item><item><title>How does BEAST work?</title><link>https://maarten.mulders.it/2018/11/how-does-beast-work/</link><pubDate>Wed, 21 Nov 2018 08:23:44 +0200</pubDate><guid>https://maarten.mulders.it/2018/11/how-does-beast-work/</guid><description>&lt;p&gt;Last month, &lt;a href="https://gotober.com/2018/sessions/684"&gt;I did a talk at GOTO Berlin&lt;/a&gt; where I explained the basics of Transport Layer Security.
During the talk, the audience asked a few questions through the app.
One of them was: &amp;ldquo;How does Beast work?&amp;rdquo; and I wasn&amp;rsquo;t able to answer that one on stage, unfortunately.
Since it&amp;rsquo;s an interesting question, I&amp;rsquo;ll answer it here.
Unfortunately, understanding BEAST is a bit harder than the talk itself&amp;hellip;&lt;/p&gt;
&lt;p&gt;BEAST stands for &lt;em&gt;Browser Exploit Against SSL/TLS&lt;/em&gt;.
In itself, it isn&amp;rsquo;t a vulnerability.
Thai Duong and Juliano Rizzo made a demonstration of a longer-known vulnerability.
This vulnerability was published &lt;a href="https://www.openssl.org/~bodo/tls-cbc.txt"&gt;back in 2004&lt;/a&gt; and applied to SSL 3.0 and TLS 1.0.
BEAST showed that this old vulnerability was in fact useable for a real-world attack.&lt;/p&gt;</description></item></channel></rss>