News for hackers. Stuff that matters.
Re:Fire destroys S. Korean government's cloud storage system... by crazygringo on Sunday October 05, 2025 @04:35PM (#45485007)
Exactly.

Like, don't store it in the cloud of an enemy country of course.

But if it's encrypted and you're keeping a live backup in a second country with a second company, ideally with a different geopolitical alignment, I don't see the problem.

Re:Fire destroys S. Korean government's cloud storage system... by manquer on Sunday October 05, 2025 @05:02PM (#45485228)
The problem is money,

you are seeing the local storage decision under the lens of security, that is not the real reason for this type of decision.

While it may have been sold that way, reality is more likely the local DC companies just lobbied for it to be kept local and cut as many corners as they needed. Both the fire and architecture show they did cut deeply.

Now why would a local company voluntary cut down its share of the pie by suggesting to backup store in a foreign country. They are going to suggest keep in country or worse as was done here literally the same facility and save/make even more !

The civil service would also prefer everything local either for nationalistic /economic reasons or if corrupt then for all kick backs each step of the way, first for the contract, next for the building permits, utilities and so on.

Re:Fire destroys S. Korean government's cloud storage system... by OvbiousError on Sunday October 05, 2025 @04:53PM (#45485160)
Enemy country in the current geopolitical climate is an interesting take. Doesn't sound like a great idea to me tbh.
Re:Fire destroys S. Korean government's cloud storage system... by deaddodo on Sunday October 05, 2025 @05:02PM (#45485231)
There are a lot of gray relations out there, but there’s almost no way you could morph the current US/SK relations to one of hostility; beyond a negligible minority of citizens in either being super vocal for some perceived slights.
Re:Fire destroys S. Korean government's cloud storage system... by gitremote on Sunday October 05, 2025 @06:16PM (#45485790)
You think when ICE arrested over 300 South Korean citizens who were setting up a Georgia Hyundai plant and subjected them to alleged human rights abuses, it was only a perceived slight?

https://www.huffpost.com/entry/south-korea-human-rights-inve...

How Trump’s ICE Raid Triggered Nationwide Outrage in South Korea

https://www.newsweek.com/trump-ice-raid-hyundai-outrage-sout...

'The raid "will do lasting damage to America's credibility," John Delury, a senior fellow at the Asia Society think tank, told Bloomberg. "How can a government that treats Koreans this way be relied upon as an 'ironclad' ally in a crisis?"'

Re:Fire destroys S. Korean government's cloud storage system... by deaddodo on Sunday October 05, 2025 @11:58PM (#45487524)
Yes.
Re:Fire destroys S. Korean government's cloud storage system... by kergonath on Sunday October 05, 2025 @06:18PM (#45485809)
One could have said the exact same thing about US-EU relations just a couple of years ago. And yet, here we are.
Re:Fire destroys S. Korean government's cloud storage system... by shantara on Sunday October 05, 2025 @05:52PM (#45485603)
A year ago, I would have easily claimed the same thing about Denmark.
Re:Fire destroys S. Korean government's cloud storage system... by throwaway2037 on Sunday October 05, 2025 @07:53PM (#45486313)
I don't follow. Can you share more context?
Re:Fire destroys S. Korean government's cloud storage system... by marcosdumay on Sunday October 05, 2025 @10:42PM (#45487165)
The US is threatening to invade Greenland, what means active war with Denmark.
Re:Fire destroys S. Korean government's cloud storage system... by throwaway2037 on Monday October 06, 2025 @11:40AM (#45492565)
Great point! I forgot that Greenland is not (yet) an independent nation. It is still a part of Denmark.
Re:Fire destroys S. Korean government's cloud storage system... by smcin on Monday October 06, 2025 @04:07PM (#45495708)
The current US admin's threats to annex Greenland, an autonomous territory of Denmark.
Re:Fire destroys S. Korean government's cloud storage system... by 9dev on Sunday October 05, 2025 @05:27PM (#45485448)
Trump will find a way, just as he did with Canada for example (i mean, Canada of all places). Things are way more in flux than they used to be. There’s no stability anymore.
Re:Fire destroys S. Korean government's cloud storage system... by vkou on Sunday October 05, 2025 @05:08PM (#45485273)
A country can become an adversary faster than a government can migrate away from it.
Re:Fire destroys S. Korean government's cloud storage system... by crazygringo on Sunday October 05, 2025 @05:26PM (#45485442)
Hence a backup country. I already covered that.

But while countries go from unfriendly to attacking you overnight, they don't generally go from friendly to attacking you overnight.

Re:Fire destroys S. Korean government's cloud storage system... by vkou on Sunday October 05, 2025 @06:12PM (#45485753)
Overnight, Canada went from being an ally of the US to being threatened by annexation (and target #1 of an economic war).

If the US wants its state-puppet corporations to be used for integral infrastructure by foreign governments, it's going to need to provide some better legal assurances than 'trust me bro'.

(Some laws on the books, and a congress and a SCOTUS that has demonstrated a willingness to enforce those laws against a rogue executive would be a good start.)

Re:Fire destroys S. Korean government's cloud storage system... by t-3 on Sunday October 05, 2025 @05:00PM (#45485205)
From the perspective of securing your data, what's the practical difference between a second country and an enemy country? None. Even if it's encrypted data, all encryption can be broken, and so we must assume it will be broken. Sensitive data shouldn't touch outside systems, period, no matter what encryption.
Re:Fire destroys S. Korean government's cloud storage system... by Avamander on Sunday October 05, 2025 @05:17PM (#45485360)
Any even remotely proper symmetric encryption scheme "can be broken" but only if you have a theoretical adversary with nearly infinite power and time, which is in practice absolutely utterly impossible.

I'm sure cryptographers would love to know what makes it possible for you to assume that say AES-256 or AES-512 can be broken in practice for you to include it in your risk assessment.

Re:Fire destroys S. Korean government's cloud storage system... by 9dev on Sunday October 05, 2025 @05:25PM (#45485433)
You’re assuming we don’t get better at building faster computers and decryption techniques. If an adversary gets hold of your encrypted data now, they can just shelf it until cracking becomes eventually possible in a few decades. And as we’re talking about literal state secrets here, they may very well still be valuable by then.
Re:Fire destroys S. Korean government's cloud storage system... by stavros on Sunday October 05, 2025 @05:44PM (#45485549)
Barring any theoretical breakthroughs, AES can't be broken any time soon even if you turned every atom in the universe into a computer and had them all cracking all the time. There was a paper that does the math.
Re:Fire destroys S. Korean government's cloud storage system... by Avamander on Sunday October 05, 2025 @05:45PM (#45485551)
You make an incorrect assumption about my assumptions. Faster computers or decryption techniques will never fundamentally "break" symmetric encryption. There's no discrete logarithm or factorization problem to speed up. Someone might find ways to make for example AES key recovery somewhat faster, but the margin of safety in those cases is still incredibly vast. In the end there's such an unfathomably vast key space to search through.
Re:Fire destroys S. Korean government's cloud storage system... by immibis on Monday October 06, 2025 @06:07AM (#45489678)
You're also assuming nobody finds a fundamental flaw in AES that allows data to be decrypted without knowing the key and much faster than brute force. It's pretty likely there isn't one, but a tiny probability multiplied by a massive impact can still land on the side of "don't do it".
Re:Fire destroys S. Korean government's cloud storage system... by Avamander on Monday October 06, 2025 @08:44AM (#45490755)
I'm not. It's just that the math behind AES is very fundamental and incredibly solid compared to a lot of other (asymmetric) cryptographic schemes in use today. Calling the chances of it tiny instead of nearly nonexistent sabotages almost all risk assessments. Especially if it then overshadows other parts of that assessment (like data loss). Even if someone found "new math" and it takes very optimistically 60 years, of what value is that data then? It's not an useful risk assessment if you assess it over infinite time.

But you could also go with something like OTP and then it's actually fundamentally unbreakable. If the data truly is that important, surely double the storage cost would also be worth it.

Re:Fire destroys S. Korean government's cloud storage system... by XorNot on Sunday October 05, 2025 @06:11PM (#45485746)
The risk that the key leaks through an implementation bug or a human intelligence source.

Exfiltrating terabytes of data is difficult, exfiltrating 32 bytes is much less so.

Re:Fire destroys S. Korean government's cloud storage system... by Avamander on Sunday October 05, 2025 @06:14PM (#45485765)
That's very far from the encryption itself being broken though. If that were the claim, I would have had no complaints.
Re:Fire destroys S. Korean government's cloud storage system... by VirusNewbie on Sunday October 05, 2025 @06:19PM (#45485810)
A statement like "all encryption can be broken" is about as useful as "all systems can be hacked" in which case, not putting data in the cloud isn't really a useful argument.
Re:Fire destroys S. Korean government's cloud storage system... by crazygringo on Sunday October 05, 2025 @05:24PM (#45485423)
> From the perspective of securing your data, what's the practical difference between a second country and an enemy country? None.

Huh? An enemy country will shut off your access. Friendly countries don't.

> Even if it's encrypted data, all encryption can be broken, and so we must assume it will be broken.

This is a very, very hot take.