News for hackers. Stuff that matters.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by gamache on Tuesday September 06, 2016 @08:54AM (#12435578)
> Know this: Krypton is more than just a blockchain or another cryptocurrency. We will survive these attacks, even if it means staying on the POS chain, in order to protect KR investments, until we do the complete rewrite of our client platform in a more secure language, like C.

What could possibly go wrong?

Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by beberlei on Tuesday September 06, 2016 @09:14AM (#12435725)
I was scared by the mention of migrating all code from etherum to bitcoin blockchain in just one night.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by mehh on Tuesday September 06, 2016 @08:58AM (#12435609)
Funny, was literally about to post the same thing!
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by tremon on Tuesday September 06, 2016 @09:16AM (#12435743)
Any chance this was meant as sarcasm? As in, they're suggesting that even C is more secure than what Ethereum has developed?
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by heliumcraft on Tuesday September 06, 2016 @09:27AM (#12435801)
It has nothing to do with Ethereum. This Krypton chain has a very minuscule hashpower so it's susceptible to attacks. It would happen with any Proof of Work chain. She is moving to a Proof of Stake which requires +- 51% of the ownership total coins to execute an attack like this.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by andrewvijay on Tuesday September 06, 2016 @09:14AM (#12435723)
Same thought. But then may be Krypton Dev is wise enough to sort out his stuff.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by gamache on Tuesday September 06, 2016 @09:20AM (#12435765)
A great hacker could maybe do it in C -- maybe even in a one-night coding spree -- but a wise hacker in 2016 wouldn't try.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by smitherfield on Tuesday September 06, 2016 @09:54AM (#12435986)
C can be secure if you follow best practices (yes, big if). Are BSD, Linux and Postgres secure?
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by geofft on Tuesday September 06, 2016 @11:17AM (#12436594)
Postgres isn't written in standard C. It's written in a derivative of C where signed integer overflow is defined as two's-complement and the strict aliasing rule is removed. Most standard C compilers also support this variant language with the compile options -fwrapv -fno-strict-aliasing.

https://www.postgresql.org/message-id/[email protected]...

If you're going to use Postgres as an example of writing secure code in a language, that's fine, but make sure you're advocating for this C variant and not for standard C. Standard C, where signed integer overflow is undefined and the strict aliasing rule exists, is extremely hard to write secure code in.

http://blog.regehr.org/archives/1307

(There's also the separate issue that most of the input paths into Postgres are trusted in some way: you don't expect malformed database files, and you often don't expect hostile queries. It's primarily the auth code that needs to be rock-solid, which is a relatively small piece of the software.)

Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by anarazel on Tuesday September 06, 2016 @04:47PM (#12439187)
Yea, postgres certainly assumes a lot more than the standard guarantees. Besides the above, if you look at it formally, it's pretty much impossible to have a multi-process program, connected over shared memory, that's actually fully standard compliant. Especially not when using a pre C11 environment (postgres requires C89).

I think we really should have "official" variants of C that are a bit more predictable. But I guess that's not happening.

Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by anarazel on Tuesday September 06, 2016 @04:52PM (#12439215)
Oh, and whoever designed the strict aliasing specs: To me they seem widely impractical. The fact that there's essentially no way to explicitly alias, without memcpy'ing, is just absurd. The standard's language is also so cryptic, that well versed people (like Regehr you linked to) can't agree with each other what the exact requirements are. The union aliasing trick isn't, to my knowledge, actually precisely standards conforming.
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by nl on Tuesday September 06, 2016 @12:37PM (#12437251)
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by zenlikethat on Tuesday September 06, 2016 @10:21AM (#12436178)
Which BSD? Postgres "maybe", Linux hell no. Constant kernel exploits
Re:Krypton Abandons Ethereum-Based Blockchain After 51% Attack by kl4m on Tuesday September 06, 2016 @10:11AM (#12436121)
Maybe