“Mr. Jacob Torrey joined DARPA as a program manager in May 2017.”
http://www.darpa.mil/staff/mr-jacob-torrey
Jacob is also the creator of the Firmware-Security list on Twitter.
https://www.jacobtorrey.com/ (expired HTTPS cert)
“Mr. Jacob Torrey joined DARPA as a program manager in May 2017.”
http://www.darpa.mil/staff/mr-jacob-torrey
Jacob is also the creator of the Firmware-Security list on Twitter.
https://www.jacobtorrey.com/ (expired HTTPS cert)
Back when this blog was first started, Jacob Torrey created a firmware-security list on Twitter to help. Newer readers of the blog may not be aware of that list. If you’re on Twitter, and have sources of firmware news, please consider using that list. Thanks.
Jacob Torrey has a presentation on ROWHAMMER:
https://twitter.com/JacobTorrey/status/789830356652462080
[…] Earlier this year at TROOPERS I presented on how many tenets of the LangSec theories could be integrated into a modern SDLC through providing a framework for “verification-oriented programming”. This idea revolved around the notion that “to err is human, to be caught at compile-time (or as close to it as possible) divine”, and that developers are going to make mistakes, but a good SDLC should be able to catch those bugs rapidly. […]
Earlier I was starting to create a list of Twitter feeds of firmware-related security researchers, since many use Twitter exclusively these days. But I have been hesitant to continue this, in case I don’t know about some researchers and not list them, etc. I’d rather let others manage the list, and luckily Jacob Torrey created a Twitter ‘firmware-security’ list so you can join yourself and I don’t have to create/maintain a list!
https://twitter.com/JacobTorrey/lists/firmware-security
In addition to Twitter, there still are a few people who use blogs. Vincent Zimmer has been blogging on firmware for a long time, and he’s got the definitive post on firmware blogs:
http://vzimmer.blogspot.com/2015/06/firmware-related-blogs.html
I don’t know anything about Usenet, IRC/XMPP/IM, Reddit, Facebook, LinkedIn, Google+, or other social network communities which cover firmware security issues. If you know of one, please leave a comment on this blog (see left), or email me (see upper right).
For a future blog post, I’ll create a list of firmware-related mailing lists.
I’m new to Twitter, still don’t have an account. A while ago I started looking into the right Twitter feeds to read:
but I’ve not updated that list in a while. Luckily for me, Jacob Torrey, one of the firmware researchers on above list the helped me out by creating (and maintaining) an EXCELLENT list of Twitter feeds for firmware research:
https://twitter.com/JacobTorrey/lists/firmware-security/members
I’ve got a lot more OEM/IHV/etc Twitter feeds since 0.3, will be working on a 0.4 release, but I can’t match Jacob’s list. Check it out!
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Discover the Desktop
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
News from coreboot world
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Hastily-written news/info on the firmware security/development communities, sorry for the typos.
Just another WordPress.com site
Hastily-written news/info on the firmware security/development communities, sorry for the typos.