Elektrine
Log in Register

#itsec

9 posts · Last used 1d

Back to Timeline
In reply to
@kkarhan@jorts.horse · 1d ago
@libreleah@mas.to nice to see #Wayland getting adopted more. Certainly neither it nor X are the main focus of it, but it's always good to see #OpenBSD not just getting maintenance but improving.I genuinely want OpenBSD to be more successful and force eberyone else to up their game in #ITsec…
0
0
0
In reply to
@kkarhan@jorts.horse · 4d ago
@javahippie@mainz.social @koehntopp@infosec.exchange @mewe@todon.eu ändert nix daran dass die #ITsec bei Bundedtag ujd Bundesregierung für'n Arsch ist!
0
0
0
In reply to
@kkarhan@jorts.horse · 4d ago
@javahippie@mainz.social ja, nur ist das das geringste Problem der #ITsec ,#InfoSec, #OpSec & #ComSec dort...
0
0
0
Boosted by Kevin Karhan @kkarhan@jorts.horse
@kubikpixel@chaos.social · 4d ago
Cryptographic Right Answers: Post Quantum and Rust Edition […] Cryptography is everywhere and as a developer you will need to upgrade your projects with post-quantum algorithms, whether because you care about the security of your users, or for compliance reasons. […] 🦀 https://kerkour.com/post-quantum-cryptography-recommendations-rust #rust #cryptography #rustlang #pqc #itsec #itsecurity #security #coding #PQCryptography #postquantum
6
0
6
In reply to
@kkarhan@jorts.horse · 5d ago
@javahippie@mainz.social ändert trotzdem nix daran dass @Bundesregierung@social.bund.de miserable #ITsec, #InfoSec, #OpSec & #ComSec haben. Also wirklich miserabel…Und nein ich kann nicht ins Detail gehen. Nacher Ende ich wie Boris "Tron" Floricic…
0
0
0
In reply to
@kkarhan@jorts.horse · 5d ago
@markus_netzpolitik@chaos.social @oldperl@mastodon.online am Ende entscheide ich das nicht. @Bundesregierung@social.bund.de & @bsi@social.bund.de steht es ja frei entsprechend Mittel für Planstellen freizuschaufeln damit nicht erst alles bei @certbund@social.bund.de aufschlägt.Gern mach' ich auch nen #Onboarding damit die #ITsec, #InfoSec, #OpSec & #ComSec nicht mehr komplett für die Tonne ist, denn das was ich an #OSINT bisher ohne #NDA rausfinden konnte ist erschreckend!So "@Lilith@chaos.social würde wahrscheinlich untertauchen müssen" - Level…
1
0
0
In reply to
@kkarhan@jorts.horse · 5d ago
@evawolfangel@chaos.social I wish they'd get serious #GDPR fines and be forced to reimburse everyone's costs and damages to change these and the harm caused by said #DataBreach. Cuz #LackOfAccountability & #LackOfConsequences embolden companies to not take #ITsec & #InfoSec serious…
0
0
0
@kkarhan@jorts.horse · 6d ago
It's really a.missed chance by #Samsung that they don't use 123.45.67.89 as their own #DNS resolver & default for their devices. Cuz they actually have that one allocated by #APNIC and #WHOIS literally says it's in #Gangnam! Don't believe me? Look it up! #DNSserver #DNSresolver #Resolvers #GangnamStyle #ITsec #Meme #Memes #IT #Networkin #ItsNeverDNS #ItsAlwaysDNS #itsDNS
4
0
2
@Larvitz__dup_34529@burningboard.net · Feb 12, 2026
Stop running setenforce 0 and pretending SELinux doesn't exist. I wrote a practical guide to actually working with SELinux on Fedora and RHEL: Contexts, booleans, troubleshooting denials, container volume labels, and the commands you'll actually use. No policy theory rabbit holes. Just the stuff that gets you unstuck. https://blog.hofstede.it/selinux-a-practical-guide-for-fedora-and-rhel/ #SELinux #Fedora #RHEL #Linux #sysadmin #infosec #itsec
0
0
0

You've seen all posts