Live data from Hacker News

The curious case of the Raspberry Pi in the network closet (2019)

blog.haschek.at

21–30 of 269 posts

Re: The curious case of the Raspberry Pi in the network closet (2019)

#21
post #3

Author of the article here. Since I first published this blog post I was getting messages from people asking how it ended. Sadly it's pretty anticlimactic as the owner of the place had a meeting with the guy who put the Pi there (without me as he didn't want the Pi-dropper to feel ambushed) and in the end decided not to escalate it to legal and just basically told him to pack his things and get out. So no legal after…

> So no legal after play and just a slap on the wrist

The problem with this is you have no idea what harm the guy actually may have caused; nor what other RPis he may have set up around the company or around town. Next time he may be more careful with his username, set up the disk to be encrypted w/ a network key, &c, making future exploits more difficult to track down.

Re: The curious case of the Raspberry Pi in the network closet (2019)

#22
post #13

I'm rather curious, why can't the RPi have soldered flash memory? How much would it cost to add 2, 4, or 8GB of flash memory on it? Because I would gladly pay for a Rpi with such memory if it added 10 dollars. I'm suspecting it would require for them to make a new SOC, breaking compability?

Compute module has eMMC, and they haven’t been excessively costly because of it or reportedly unreliable in the way SDs are. But either way I suspect that the Foundation design team has some issues in designing power circuits rather than that SD cards being unfit or people are throwing in cheap ones.

Re: The curious case of the Raspberry Pi in the network closet (2019)

#24
post #21
post #3

Author of the article here. Since I first published this blog post I was getting messages from people asking how it ended. Sadly it's pretty anticlimactic as the owner of the place had a meeting with the guy who put the Pi there (without me as he didn't want the Pi-dropper to feel ambushed) and in the end decided not to escalate it to legal and just basically told him to pack his things and get out. So no legal after…

> So no legal after play and just a slap on the wrist The problem with this is you have no idea what harm the guy actually may have caused; nor what other RPis he may have set up around the company or around town. Next time he may be more careful with his username, set up the disk to be encrypted w/ a network key, &c, making future exploits more difficult to track down.

This, truly, is the thing to worry about: if it happened here, it likely happened at other companies. Turning a blind eye is a blank check to do it again.

Re: The curious case of the Raspberry Pi in the network closet (2019)

#25
post #3

Author of the article here. Since I first published this blog post I was getting messages from people asking how it ended. Sadly it's pretty anticlimactic as the owner of the place had a meeting with the guy who put the Pi there (without me as he didn't want the Pi-dropper to feel ambushed) and in the end decided not to escalate it to legal and just basically told him to pack his things and get out. So no legal after…

omg, that guy got of the hook easy. he should play the lottery considering how lucky this was.

Re: The curious case of the Raspberry Pi in the network closet (2019)

#26

Reminds me of this[1] good old quote from the IRC days hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. [1]: http://bash.org/?5273

I've also had this problem once, on a university campus though.

"net send 'If you can read this, please call IT SUPPORT at ... and tell us'".

It worked :)

Re: The curious case of the Raspberry Pi in the network closet (2019)

#27
That's a very obvious and very obviously bad way of planting a network exploit. Very rookie and rather sad.

In entirely unrelated news, this guide details how to set up an encrypted boot process on a raspberry pi, with it waiting for you(r forked login agent) to ssh in and provide the LUKS password: https://github.com/ViRb3/pi-encrypted-boot-ssh

Re: The curious case of the Raspberry Pi in the network closet (2019)

#28
post #26

Reminds me of this[1] good old quote from the IRC days hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. [1]: http://bash.org/?5273

I've also had this problem once, on a university campus though. "net send 'If you can read this, please call IT SUPPORT at ... and tell us'". It worked :)

This should really only ever happen with wireless connections. You should always be able to tell what switchport a computer is connected to and work from there.

Re: The curious case of the Raspberry Pi in the network closet (2019)

#30
post #21

Earlier quoted context omitted.

> So no legal after play and just a slap on the wrist The problem with this is you have no idea what harm the guy actually may have caused; nor what other RPis he may have set up around the company or around town. Next time he may be more careful with his username, set up the disk to be encrypted w/ a network key, &c, making future exploits more difficult to track down.

This, truly, is the thing to worry about: if it happened here, it likely happened at other companies. Turning a blind eye is a blank check to do it again.

The issue here is that this isn't just "one bad apple" that if we can remove everything will be ok. Which is what motivates the idea that punishing this bad actor will make everything better.

There is a systematic issue at the heart of the way we do network security.

You can by a lighting / usb cable that can do all of these things and more for $120 if he'd used that he'd never have gotten caught.

We treat network security like physical security at our peril.

Post reply on HN