Live data from Hacker News

Entropic Engineering DEFCON 32 Statement

entropicengineering.com

181–187 of 187 posts

Re: Entropic Engineering DEFCON 32 Statement

#181
post #153

Earlier quoted context omitted.

I might be misunderstanding what was embeeded, but since the author stating that they put the is in “as a joke” in the same context they were explaining that they basically were not working on behalf of entropic and “just doing it cause I wanted people to have badges” I was under the assumption that the crypto wallet was controlled by the author. In any case, putting a tip screen in software you’re creating for other…

For reference, here’s the screen: https://imgur.com/Qy7iPKE I don’t know if the wallet belongs to Entropic or Dmitry and he intended to forward the money to them.

> and he intended to forward the money to them.

That’s just a cop out and we all know it. Let’s not pretend like scammers aren’t scammers be used they might pass some money after the fact to “good causes”. If you inject a fund collecting mechanism that you control into a flow, that’s like doing a MITM attack but claiming it’s ok because you forward the traffic.

Re: Entropic Engineering DEFCON 32 Statement

#182
post #155
post #79

Earlier quoted context omitted.

At DEFCON of all places. I mean, they steal your password and post it on a board as a joke. Didn't someone set up fake charging devices a few years ago to hack people's phone and gave a talk about it?

Which password?

Hunter2

Re: Entropic Engineering DEFCON 32 Statement

#183

Earlier quoted context omitted.

It’s none of our business. He is some sort of poorman’s vigilante and even embedding an unauthorized Easter egg with a BTC address.

> It’s none of our business. Thank you for your opinion. I will decide what is my business and what is not.

Thank you for your opinion.

Re: Entropic Engineering DEFCON 32 Statement

#184

Earlier quoted context omitted.

The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON.

>The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON. Defcon stopped paying and talking. They would have brushed this all under a rug

EE went way over budget. DEFCON was right to cancel the contract.

What’s your involvement anyways besides a free contributor to the emulator?

Re: Entropic Engineering DEFCON 32 Statement

#185

Earlier quoted context omitted.

>The firmware developer is really the one causing most of the problems. If not for him, this would have handled amicably between EE and DEFCON. Defcon stopped paying and talking. They would have brushed this all under a rug

EE went way over budget. DEFCON was right to cancel the contract. What’s your involvement anyways besides a free contributor to the emulator?

"contributor" implies someone else participated, i feel i have been clear about the fact that every single bit of the firmware was my work. Nobody else worked on it.

Re: Entropic Engineering DEFCON 32 Statement

#186

Earlier quoted context omitted.

EE went way over budget. DEFCON was right to cancel the contract. What’s your involvement anyways besides a free contributor to the emulator?

"contributor" implies someone else participated, i feel i have been clear about the fact that every single bit of the firmware was my work. Nobody else worked on it.

Your work that you gave away. No more data rights on the executable.
Post reply on HN