Twitter | Search | |
Filippo Bigarella
Security & Privacy MSc student . Software engineer with a focus on security (iOS/macOS).
13,112
Tweets
244
Following
24,103
Followers
Tweets
Filippo Bigarella Jan 7
Replying to @revskills
Sometimes even remotely replicating what has been done is extremely challenging (missing implementation details, leaky abstractions that do not fit the real world, etc…), let alone achieving the same results :(
Reply Retweet Like
Filippo Bigarella retweeted
Emiliano DC Jan 5
Probably stating the obvious but vulnerabilities like Spectre and Meltdown is yet another reason why "applied crypto is dead, SGX solves everything" is BS.
Reply Retweet Like
Filippo Bigarella Jan 4
Replying to @FredericJacobs
Are you implying that Intel 8008 are also affected? Asking for a friend ;P
Reply Retweet Like
Filippo Bigarella Jan 3
Personally, this is something that stands out from a brief skim through the Spectre paper: not just a flaw, but a completely new technique to break security boundaries which, I guess, is only bound to get better.
Reply Retweet Like
Filippo Bigarella Jan 3
Also, it seems Twitter is now full of processor internals experts. Which makes me wonder why these issues have not been discovered >10 years ago? 😛
Reply Retweet Like
Filippo Bigarella Jan 3
As half of the world already said: congrats to all the researchers involved in Meltdown and Spectre. Amazing work, looks I know have quite a bit of stuff to learn :)
Reply Retweet Like
Filippo Bigarella Jan 3
Replying to @stm_dev
It was not booting to either. :(
Reply Retweet Like
Filippo Bigarella retweeted
brainsmoke Jan 3
Reply Retweet Like
Filippo Bigarella Jan 1
Replying to @alastair_d_reid
Beautiful intern project. Has there been any publication about it?
Reply Retweet Like
Filippo Bigarella Dec 30
Thank you so much for your talk at 34C3. Extremely informative – I really liked the idea of fuzzing with internal feedback.
Reply Retweet Like
Filippo Bigarella Dec 29
Replying to @revskills
You should get to OffensiveCon or TROOPERS :)
Reply Retweet Like
Filippo Bigarella Dec 29
Replying to @teejay_1987
Purtroppo non ho più il Mac sottomano, lo porteranno ad Apple e vediamo che dicono. Ho ipotizzato il disco e/o connettore andati anche io.
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @JMoVS
Well it did twice, but after the “restore” it boots to the question mark folder. So now I think it’s either the disk or the connector.
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @ronaldsb
Nope!
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @_imakeitgood
No key combination seems to be working, it just booted to internet recovery after ~2 hours of being stuck at a black screen ¯\_(ツ)_/¯
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @_imakeitgood
Likely, but that doesn’t explain why it doesn’t boot to recovery nor target disk mode :/
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @FilippoBiga
Update: it booted to internet recovery after 2 hours; did its magic and then got to the question mark folder. At least I know there’s still something *alive* in there.
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @SwissHttp
Well, I guess they need to improve their QA then… check if the platform is supported before install? ;P
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @bigb8242
MacBook Air, and yep, hangs at black screen after the boot sound.
Reply Retweet Like
Filippo Bigarella Dec 27
Replying to @ichanzonly
I honestly hope it’s something else ;P
Reply Retweet Like