Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

205
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#https

3 posts3 participants0 posts today
beSpacific<p>2)This is a <a href="https://newsie.social/tags/Lie" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Lie</span></a> - Crime is Down in DC <a href="https://newsie.social/tags/Trump" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Trump</span></a> Declares a <a href="https://newsie.social/tags/Crime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Crime</span></a> <a href="https://newsie.social/tags/Emergency" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Emergency</span></a> to Restore Safety in the <a href="https://newsie.social/tags/DistrictofColumbia" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DistrictofColumbia</span></a> - using insanely stupid <a href="https://newsie.social/tags/url" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>url</span></a> <a href="https://newsie.social/tags/coverup" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>coverup</span></a> <a href="https://newsie.social/tags/distraction" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>distraction</span></a> <a href="https://newsie.social/tags/corruption" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>corruption</span></a> <a href="https://newsie.social/tags/DOJ" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DOJ</span></a> <a href="https://newsie.social/tags/NationalGuard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NationalGuard</span></a> <a href="https://newsie.social/tags/militarization" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>militarization</span></a> <a href="https://newsie.social/tags/fascism" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fascism</span></a> <a href="https://newsie.social/tags/dictator" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dictator</span></a> <a href="https://newsie.social/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>https</span></a>://www.whitehouse.gov/fact-sheets/2025/08/fact-sheet-president-donald-j-trump-declares-a-crime-emergency-to-restore-safety-in-the-district-of-columbia/#:~:text=Executive%20Order%20declaring%20a%20crime%20emergency%20in%20the%20District%20of%20Columbia</p>
Dendrobatus Azureus<p>As I am browsing through the settings in firefox I see the odd setting of using it's own DNS over https enabled. My settings should be copied over from the account I use and I know that I've **never** turned this setting on.</p><p>I'm now on the SBC Pi5 running MX Linux Pi respin. </p><p>My own dns config is perfectly fine and Im changing it back.</p><p>Why is the firefox team doing this? IS there any protective benifit from having this setting on?</p><p><a href="https://mastodon.bsd.cafe/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InfoSec</span></a> <a href="https://mastodon.bsd.cafe/tags/AskFediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AskFediverse</span></a> <a href="https://mastodon.bsd.cafe/tags/firefox" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firefox</span></a> <a href="https://mastodon.bsd.cafe/tags/DNS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS</span></a> <a href="https://mastodon.bsd.cafe/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>https</span></a> <a href="https://mastodon.bsd.cafe/tags/port443" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>port443</span></a> <a href="https://mastodon.bsd.cafe/tags/settings" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>settings</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></p>
c't Magazin<p>Let’s Encrypt hat OCSP-Server abgeschaltet</p><p>Zertifikate kann man bei Let’s Encrypt nicht mehr per OCSP prüfen. Wer von Problemen erfahren will, muss stattdessen Widerrufslisten konsultieren.</p><p><a href="https://www.heise.de/news/Let-s-Encrypt-hat-OCSP-Server-abgeschaltet-10514864.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">heise.de/news/Let-s-Encrypt-ha</span><span class="invisible">t-OCSP-Server-abgeschaltet-10514864.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&amp;utm_source=mastodon</span></a></p><p><a href="https://social.heise.de/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>https</span></a> <a href="https://social.heise.de/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IT</span></a> <a href="https://social.heise.de/tags/news" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>news</span></a></p>
Tommi 🤯 @ WHY 📞9848<p><strong>Can’t connect to public WiFi via Linux</strong></p><p>I am using Fedora 42, and I am unable to access the captive portal of inOui TGV. I can connect to the WiFi with no problems, but I can’t get access to the Internet.</p><p>I have tried <strong>everything</strong>:</p><ol><li>Connecting to <code>192.168.1.1</code>, to <code>http://neverssl.com</code>, to <code>http://wifi.sncf</code> via browser</li><li>Running <code>sudo dhclient -r</code> and rebooting the device</li><li>Running <code>systemctl restart NetworkManager</code></li><li>Also other stuff I tried in the past with other public WiFis. I am sure there is something wrong with my specific device configuration, it’s not this network.</li></ol><p>Nothing works 😩</p><p>Can somebody who understands this stuff help me?</p><p><a href="https://pan.rent/tags/help" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>help</span></a> <a href="https://pan.rent/tags/mastoAiuto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>mastoAiuto</span></a> <a href="https://pan.rent/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://pan.rent/tags/LinuxNetwork" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxNetwork</span></a> <a href="https://pan.rent/tags/Network" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Network</span></a> <a href="https://pan.rent/tags/CaptivePortal" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CaptivePortal</span></a> <a href="https://pan.rent/tags/WiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>WiFi</span></a> <a href="https://pan.rent/tags/PublicWiFi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PublicWiFi</span></a> <a href="https://pan.rent/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> <a href="https://pan.rent/tags/HTTPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTPS</span></a> <a href="https://pan.rent/tags/troubleshoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>troubleshoot</span></a> <a href="https://pan.rent/tags/LinuxHelp" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LinuxHelp</span></a> <a href="https://pan.rent/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fedora</span></a> <a href="https://pan.rent/tags/Fedora42" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Fedora42</span></a></p>
Erik van Straten<p><span class="h-card" translate="no"><a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jwildeboer</span></a></span> : modern certificates are used for authentication only, not for secure connections.</p><p>OTOH, if you have no certainty that your software is communicating with the server you intended, a secure connection to it is pointless - but the connection remains secure.</p><p>Using TLS v1.3, the connection is even secured before the server is authenticated (if, after encrypting the connection, the authentication of the server fails, then the client should at least warn the user - if not immediately disconnect).</p><p>Yes, I know, these are boring details, but they are misunderstood way too often by people who SHOULD know how this works (I know you do, but please don't simplify things too much).<br> </p><p><a href="https://infosec.exchange/tags/TLS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLS</span></a> <a href="https://infosec.exchange/tags/https" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>https</span></a> <a href="https://infosec.exchange/tags/X509" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>X509</span></a> <a href="https://infosec.exchange/tags/Certificates" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Certificates</span></a> <a href="https://infosec.exchange/tags/Certs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Certs</span></a> <a href="https://infosec.exchange/tags/Identification" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Identification</span></a> <a href="https://infosec.exchange/tags/Authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Authentication</span></a> <a href="https://infosec.exchange/tags/Impersonation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Impersonation</span></a> <a href="https://infosec.exchange/tags/TLSv1_3" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TLSv1_3</span></a> <a href="https://infosec.exchange/tags/ForwardSecrecy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ForwardSecrecy</span></a> <a href="https://infosec.exchange/tags/DH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DH</span></a> <a href="https://infosec.exchange/tags/DHE" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DHE</span></a> <a href="https://infosec.exchange/tags/DiffieHellman" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DiffieHellman</span></a></p>
Inautilo

#Development #Announcements
Our first IP address certificate · Let’s Encrypt starts rolling out the new option ilo.im/16530s

_____
#LetsEncrypt #CA #IpAddress #Certificate #SSL #TLS #HTTPS #WebDev #Frontend #Backend

ilo.imWe've Issued Our First IP Address CertificateSince Let’s Encrypt started issuing certificates in 2015, people have repeatedly requested the ability to get certificates for IP addresses, an option that only a few certificate authorities have offered. Until now, they’ve had to look elsewhere, because we haven’t provided that feature. Today, we’ve issued our first certificate for an IP address, as we announced we would in January. As with other new certificate features on our engineering roadmap, we’ll now start gradually rolling out this option to more and more of our subscribers.
Autiste à :ch_Vaud:🌊 #woke

https-vd.ch/2025/06/15/le-logi

Découvrez le site du #HTTPS, le nouveau nom du #PartiPirateVaudois, obligé de rompre complètement les amarres avec le #PartiPirateSuisse, y compris en abandonnant la notion de #PartiPirate, pour ne pas être traîné dans ses dérives, et profitez-en pour lire l'analyse de @sebseb01 sur le #numérique #responsable à l' @etatdevaud et l'angle mort concernant le #libre et l' #opensource.

https-vd.chLe logiciel, talon d’Achille du numérique « responsable » vaudois – HTTPS
More from Sébastien Piguet
TrendingLive feeds
About