Next proper tool every serious Information Security team needs! The attribution dice. Whenever senior mgmt asks for someone to blame we can roll the dice.
Helpful tool number 3 after the "severity pendulum" and determining the root cause by reading goat bones.
Cheap roomba!
Looking for a _young dog_
or a puppy
medium height,
alive
this supermarket pinboard notice is pure poetry
Regarding Facebook tracking non-users Mark Zuckerberg said "This kind of data collection is fundamental to how the internet works."
I'm not a networking expert but I know enough to be able to confidently say that nothing at all about this data collection is fundamental to how the Internet works. I guess he was using Silicon Valley speak where "the internet" means "huge corporations who make most of their money by selling ads and illegally collecting as much data as possible".
Coding music of the day - #Quake2 soundtrack.
Makes #javascript (well #coffeescript) bearable.
"OTOH, OpenSSL wanted concrete evidence of exploitability." <- folks, this is not what security researchers want to hear. Fixing the vulnerability will result in a better product. Just do it, if even just for code correctness sake.
In this particular case, it took the researchers around a year-and-a-half to come up with a PoC, leaving everyone insecure for that entire time (and longer as it takes time for people to patch.)
System Shock (1; the code for MacOS9 on PPC) has been open sourced:
https://github.com/NightDiveStudios/shockmac
I'm curios when the first ports to Linux (or generic SDL) on x86 will turn up :)
Wow, I totally missed this. The German Federal Office for Information Security (BSI) studied and analysed three SSL libraries (#LibreSSL, NSS and Botan).
While the BSI gave their feedback back to Botan (they fund the project), it seems they never approached LibreSSL and NSS.
Good to see that my tax money is invested into making Open Source better, however, I would expect that they treat all projects equally.
I'm finding English to be the most important language for a developer. Not C++, Python, Rust, Ruby, Go or anything like that.
English.
Learn it. Get better at it.
Your ability to communicate is paramount if you work on a team.
I for sure will never touch Pale Moon. This is absurd.
PSA: Maybe you remember http://quakesrc.org , hosting lots of Quake 1/2 and Hexen2 coding tutorials. It went down 10y ago or so.
So far there had been a mirror at http://www.quake-1.com/docs/quakesrc.org/, but that seems gone as well..
Just found another mirror: https://www.quakewiki.net/quakesrc/ :-)
NULLSQL is the best database with the most amazing write times imaginable. Put all of your data into NULLSQL today!
cat data > /dev/null
IT'S JUST THAT EASY!!!
NULLSQL uses the latest in NULLSQL technology using a combination of WRITE ONCE, READ NEVER (WORN) and Singularity Indexing so reads are fast fast FAST!
TAKE PART IN THE NULLSQL REVOLUTION TODAY!
To add insult to injury: On my system Windows Defender does *not* detect anything in those files - despite having the exact same antivirus and definition versions as people who experience the problem.
And the scanned files really are the same according to checksums..
So, people who develop on/for Windows professionally: How do you cope?!
"Yamagi Quake 2 q2ded.exe gets detected as malware by Windows Defender": https://github.com/yquake2/yquake2/issues/274
For fucks sake, can't Microsoft fix their goddamn snakeoil?!
I'm very sure this is a false positive (59 different AV scanners on virustotal.com say it's clean)..
(Unless two different people have the same malware on their system that somehow alters only this specific version of q2ded.exe - and not quake2.exe - on extraction from the zip..)
No new year plans? Come frag with us in Quake 2 on an #OpenBSD server near you, join: tintagel.pl (45.63.9.186)
Shut up and Frag!
@mulander Do you currently have a working Quake2 server?
Yamagi and me might be up for some Deathmatch (or maybe coop?) later tonight :)
Had a blast yesterday, our game was even livestreamed but sadly the streamer didn't save the video for later.
Considering leaving the server running.