Breach affecting 1M was caught only after hacker maxed out target’s storage
1–10 of 35 posts
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#2Reminds me of something similar that happened to me once a long time ago.
I hacked into a server. I wanted to take a copy of everything so I made a tar of / to wget it to computer later. Only that the disk was at >50% usage so I filled it by making the tar file. Everything stopped to work with 0 bytes left of disk space (I wasn't root) so I kinda bricked the machine. I had to walk away in shame.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#3plaintext passwords in 2019 .. it hurts to read articles like these.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#4plaintext passwords in 2019 .. it hurts to read articles like these.
These are often found in log files when people get a bit to log happy.
I've seen many smart developers accidentally log a request in an API that also happens to show the login credentials.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#5Reminds me of something similar that happened to me once a long time ago. I hacked into a server. I wanted to take a copy of everything so I made a tar of / to wget it to computer later. Only that the disk was at >50% usage so I filled it by making the tar file. Everything stopped to work with 0 bytes left of disk space (I wasn't root) so I kinda bricked the machine. I had to walk away in shame.
Don't feel bad. 1995. SunOS. Very patient boss. I did the same thing.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#6plaintext passwords in 2019 .. it hurts to read articles like these.
These are often found in log files when people get a bit to log happy. I've seen many smart developers accidentally log a request in an API that also happens to show the login credentials.
Even Google fell for that one recently.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#7Reminds me of something similar that happened to me once a long time ago. I hacked into a server. I wanted to take a copy of everything so I made a tar of / to wget it to computer later. Only that the disk was at >50% usage so I filled it by making the tar file. Everything stopped to work with 0 bytes left of disk space (I wasn't root) so I kinda bricked the machine. I had to walk away in shame.
> I had to walk away in shame.
No, you'd have walked away in shame if you had walked away in handcuffs. Don't do stupid stuff. Imnsho you got lucky that disk filled up before you could notch up a(nother?) crime.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#8Given the fair assumption that any piece of data you give to a third party system that has access to the internet will eventually be breached, I feel like we need an entirely new system for data sharing.
The problem with most of these hacks isn't usually so much that the hacked system itself has lots of valuable data, but that the data from the hacked system can be used to hack into other systems that do have valuable data. Just like we tell people to only use a different password per-site, we need the option to essentially give only tokenized versions of our data to third parties. We've started somewhat with tokenization in place of credit card numbers, but we should be able to do this in many more areas.
There are obvious difficulties here regarding how we'd handle certain fields (e.g. how do I calculate your shipping if I don't know your exact zip code), but these should still be solvable problems.
The alternative of believing that every rinky dink (or non-rinky dink) site out there will be able to keep your data secure is laughable.
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#9Reminds me of something similar that happened to me once a long time ago. I hacked into a server. I wanted to take a copy of everything so I made a tar of / to wget it to computer later. Only that the disk was at >50% usage so I filled it by making the tar file. Everything stopped to work with 0 bytes left of disk space (I wasn't root) so I kinda bricked the machine. I had to walk away in shame.
> I had to walk away in shame. No, you'd have walked away in shame if you had walked away in handcuffs. Don't do stupid stuff. Imnsho you got lucky that disk filled up before you could notch up a(nother?) crime.
What happened is arguably more stupid: by filling up the disk, 1) they definitely noticed, 2) I couldn't get what I wanted, and 3) I couldn't clean up the logs after it. Thankfully I had covered up my steps (or, more probably, the sysadmin was ashamed to see he had been hacked and chose to fix it and say nothing).
Re: Breach affecting 1M was caught only after hacker maxed out target’s storage
#10Earlier quoted context omitted.
> I had to walk away in shame. No, you'd have walked away in shame if you had walked away in handcuffs. Don't do stupid stuff. Imnsho you got lucky that disk filled up before you could notch up a(nother?) crime.
What happened is arguably more stupid: by filling up the disk, 1) they definitely noticed, 2) I couldn't get what I wanted, and 3) I couldn't clean up the logs after it. Thankfully I had covered up my steps (or, more probably, the sysadmin was ashamed to see he had been hacked and chose to fix it and say nothing).
I hope you learned and not just to use 'df' more often.