ransford
I've been volunteering with Unloop for a few months, as both a guest speaker and 1:1 coach. I feel myself becoming less cynical about tech with every interaction.
Taking a job in an industry to get access to its seedy underbelly isn't super appealing to most founders, but for some ossified industries there's really no other way to find those golden opportunities.
Oh, and be patient. Practice being a mouthless set of ears.
Feynman doesn't say what, if anything, he told Webb, but it's an interesting backstory -- it's possible Webb knew more than this article suggests.
[1] https://books.google.com/books?id=_gA_DwAAQBAJ&pg=PT125&lpg=...
[1] https://web.archive.org/web/20060831053126/http://pdos.csail...
If you are interested in the challenges of harvesting energy from Wi-Fi and some ways to address those challenges, here's a nice paper (originally in CoNEXT 2015) from a team I was fortunate to be on: https://cacm.acm.org/magazines/2017/3/213830-powering-the-ne...
[Edit: the relevance here is that, even with an awesome antenna like the one in the news, the Wi-Fi protocol kinda works against you, which raises a bunch of interesting questions.]
As an industry of thing-makers, we've done a pretty poor job of supporting use cases involving big diverse populations of devices that aren't centrally managed. Devices don't identify themselves in any consistent way; device makers don't allocate MAC addresses predictably from their assigned ranges; security folks often don't have link-layer visibility into their own networks; and so on.
Result: hospitals are desperate to "secure" their medical devices, yet they don't know what those devices are, what patch levels they're at, or what their "baseline" behavior is supposed to be, among other things that are crucial for security.
The security industry has decided that medical devices are a special case of IoT, and you can now choose from a wide variety of AI blinky boxes to send you anomaly alerts. That has been going about as well as it does in other domains.
Two things that may help hospital tech workers in the coming years are: efforts like IETF's MUD [1] to make devices state their purpose clearly; and efforts like the NTIA's software transparency initiative [2] that are aiming to make manufacturers say what's in their devices. The FDA is also cracking the whip on medical device makers to incorporate security into their development processes, and they love comments from nerds who can help.
</soapbox>
(I am one of the academic researchers behind the defibrillator hacking [3] that inspired the Homeland episode mentioned in this article, and I've been cutting my fingers on innumerable sharp corners in hospital wiring closets on and off since then.)
[1] https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/
[2] https://www.ntia.doc.gov/SoftwareTransparency
[3] https://www.secure-medicine.org/hubfs/public/publications/ic...
"Let's immediately set up a separate domain name that looks like ours" remains one of the weirdest antipatterns in incident response.
[1] http://news.marriott.com/2018/11/marriott-announces-starwood...