That was probably close to one of the last versions of enlightenment I used regularly. It was such a fun WM to use at the time. If I remember correctly, GNOME and KDE were really ramping up about then and e fell behind.
That was probably close to one of the last versions of enlightenment I used regularly. It was such a fun WM to use at the time. If I remember correctly, GNOME and KDE were really ramping up about then and e fell behind.
Seems very similar to Zenbleed in terms of using certain register optimisation and speculative execution to get crippling security exploits. Thus far I haven’t read too much into the detail of the attack but This article on Zenbleed, written by the attack’s author, describes how the attack in detail and how he came to find it using fuzzing techniques - in this case two sets of instructions that should have had the same result, but they didn’t.
The write-up for this one is presumably this one.
Here is a good write-up of Zenbleed for the Ryzen 2 and up vulnerability. It uses similar register optimisation and speculative execution to get the same effect.
Not really, here’s why:
That’s why I didn’t go for that thankless job.
deleted by creator
Its alright, I’m sure the atomic clocks in orbit will notice.
Engine-rich combustion.
Great answer, it is similar to the cost parameter for bcrypt/scrypt and iterations for PBKDF2.
Ahh, the good old days.
I will date you! Though I’m younger than him. Does that count? /s
None of those categories are mutually exclusive when you use the tilde-30, especially.
Mostly I just wanted to make sure people who dislike updating, ‘because it might break stuff’ - are warned before hosting a lemmy instance. Do it on snapshot-able or reliable hardware if you are going to have people join.
Indeed. You can tell if it’s straight out of Googong Dam also.