#dnscap v2.3.0 released!
- New output format `tcpdns`
- New plugin `asudp`
- Added support for DLT_LINUX_SLL2
and fixes...
^JL
#DNS #Capture #PCAP #OpenSource
https://github.com/DNS-OARC/dnscap/releases/tag/v2.3.0
#dnscap v2.3.0 released!
- New output format `tcpdns`
- New plugin `asudp`
- Added support for DLT_LINUX_SLL2
and fixes...
^JL
#DNS #Capture #PCAP #OpenSource
https://github.com/DNS-OARC/dnscap/releases/tag/v2.3.0
heise+ | Vertrauenswürdige E-Mail: Spoofing-Schutz über DNS einrichten
Domain-Inhaber können E-Mail-Spoofing deutlich erschweren, wenn sie über das Domain Name System (DNS) standardisierte Informationen zur Verfügung stellen.
correct HTTPS (SVCB) record support is still a distant dream for Firefox and chrome. So #AWS adding static IPs to cloudfront will be welcome for many customers.
Natch AWS mangles #DNS terms in the announcement, but the feature is good anyways.
https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-cloudfront-anycast-static-ips-apex-domains/
Meine Datenschutz und Privatsphäre Übersicht 2025, für die Allgemeinheit
Teilen erbeten
als PDF:
https://cryptpad.digitalcourage.de/file/#/2/file/pIOSst7Z53pFECyng-lX9LlQ/
#DSGVO #TDDDG ( #unplugtrump )
#Datenschutz #Privatsphäre #sicherheit #Verschlüsselung
#encryption #WEtell #SoloKey #NitroKey #Email #Cybersecurity #Pixelfed #Massenűberwachung
#Google #Metadaten #WhatsApp #Threema #Cryptpad #Signal
#Hateaid #Cyberstalking #Messenger #Browser #Youtube #NewPipe #Chatkontrolle #nichtszuverbergen #ÜberwachungsKapitalismus #Microsoft #Apple #Windows #Linux #Matrix #Mastodon #Friendica #Fediverse #Mastodir #Loops #2FA #Ransomware #Foss #VeraCrypt #HateAid #Coreboot #Volksverpetzer #Netzpolitik #Digitalisierung #FragdenStaat #Shiftphone #OpenSource #GrapheneOS #CCC #Mail #Mullvad #PGP #GnuPG #DNS #Gaming #linuxgaming #Lutris #Protondb #eOS #Enshittification
#Bloatware #TPM #Murena #LiberaPay #GnuTaler #Taler #PreppingforFuture
#FediLZ #BlueLZ #InstaLZ #ThreatModel
#FLOSS #UEFI #Medienkompetenz
So an update pushed out to stuff.co.nz over the last couple of days has made it pretty much unusable due to additional tracking/surveillance capitalism. Links from front page are not fetchable anymore if you sanitize #DNS / cookies etc #NewZealand #media usual agent switching techniques don't fix it - and it does it across the three browsers I tested.
TLDR: I will never again use XYZ owned domains
What a fucking debacle. I purchased a cheap .quest domain to run my xmpp server on for my family and a few close friends. It was on sale, was cheap and I grabbed it.#WebinarPiF – Alessandro Fiorotto – Tophost, Seeweb – Il nome a dominio, la porta d'accesso al mondo digitale libero
“Your device has been blocked due to illegal activity” — sure it has. After fat-fingering github[.]com, we were redirected to a domain running a fake Microsoft tech support scams: pop-ups that lock your browser, shout scary messages, and push you to call a “support” number (aka the scammer who’ll walk you through installing remote access tools).
They're hosted on legit infra like Azure blobs or Cloudflare Pages. That one redirect led to uncovering 1,200+ other domains hosting identical fake support pages. Of course, whenever a redirect like this happens, there's a malicious traffic distribution system (TDS) involved.
Examples include:
- tenecitur.z1.web.core.windows[.]net
- neon-kleicha-36b137[.]netlify[.]app
- us6fixyourwindowsnow[.]pages[.]dev
- microsoft-coral-app-6xv89.ondigitalocean[.]app
#dnsjit v1.5.0 released!
- Added `Label.torfc1035()`
- Added support for DLT_LINUX_SLL2
- Fixed UDP & IP packet padding calculations
^JL
#DNS #Lua #Script #LuaJIT #OpenSource
https://github.com/DNS-OARC/dnsjit/releases/tag/v1.5.0
DNSControl is an opinionated platform for seamlessly managing your DNS configuration across any number of DNS hosts, both in the cloud or in your own infrastructure. It manages all of the domains for the #StackOverflow network,
#dns
https://dnscontrol.org/
We’re seeing an increasing volume of blocked queries to the SocGholish-related domain - blackshelter[.]org in the last several days.
More #poser improvements:
* Use arc4random() if available, avoids excessive syscalls just to get high-quality random data
* Add a "resolver" to do #reverse #DNS lookups in a batch, remove the reverse lookup stuff from the connection which was often useless anyways, when a short-lived connection was deleted before resolving could finish
As a result, #swad can now reliably log requests with reverse lookups enabled
Kann jemand bestätigen oder widerlegen, dass sowohl
dns3.digitalcourage.de - 5.9.164.112
und
fdns1.dismail.de - 80.241.218.68
nicht erreichbar sind??
Je viens de présenter le #DNS aux collégiens des Cordées de la Réussite :-) https://www.education.gouv.fr/les-cordees-de-la-reussite-permettre-aux-eleves-de-batir-et-de-concretiser-un-projet-d-orientation-306210
How efficient and useful are DNS block lists? I've done it for years but recently found this really cool database and effort providing massive lists, and multiple usecases that ultimately do the same thing. Whether computer, or network wide. There's a few different options.
Here's the page. Totally worth it.
https://github.com/hagezi/dns-blocklists
The auto roll of a new cert is not the problem.
The problem is why it was compromised in the first place.
It is Security Theatre. A bandaid to obscure bad security process.