Live data from Hacker News

ATM NFC Hack

wired.com

31–37 of 37 posts

Re: ATM NFC Hack

#31
post #3

Yet another buffer overflow. Probably the software is written by some C/C++ developers who swear that those never occur in their code. Given the large number of security problems that have been caused by buffer overflows and similar problems, I find it very sad that any programs that need security are still written in C/C++.

Please don’t skip the prove hypothesis part when drawing conclusions. It’s at best disingenuous.

Re: ATM NFC Hack

#32
post #30

Earlier quoted context omitted.

While you're technically correct, your ignoring the pragmatic truth: most developers are terrible and should never write code. Because of this reality, C/C++ and all its footguns are something to be avoided unless there is no other alternative (usually this happens when integrating with legacy software or in industries like gaming where the switching costs are extreme).

So you're saying that since we're encouraging people to flood the market with little to no skill, we should instead accommodate them with Baby's First Programming Language and then force all of the other developers to follow the same methodology? This makes no sense. It just sounds like Go.

Not the OP but we should weed out all the incompetent folk ASAP rather than hide it to maintain delivery speed.

Re: ATM NFC Hack

#33
post #32
post #30

Earlier quoted context omitted.

So you're saying that since we're encouraging people to flood the market with little to no skill, we should instead accommodate them with Baby's First Programming Language and then force all of the other developers to follow the same methodology? This makes no sense. It just sounds like Go.

Not the OP but we should weed out all the incompetent folk ASAP rather than hide it to maintain delivery speed.

I completely agree.

Re: ATM NFC Hack

#34
post #5

Earlier quoted context omitted.

C/C++ isn't the issue, it's the lack of not using memory-safe features like smart pointers which you'll need C++ for.

While you're technically correct, your ignoring the pragmatic truth: most developers are terrible and should never write code. Because of this reality, C/C++ and all its footguns are something to be avoided unless there is no other alternative (usually this happens when integrating with legacy software or in industries like gaming where the switching costs are extreme).

terrible programmers ain't nothing new though and large corp in critical fields are aware of that and have (or had) structural mitigations (slow and heavy processes, regulations etc)

Re: ATM NFC Hack

#36
post #29

Earlier quoted context omitted.

By this logic no C or C++ developer in history is a professional programmer. Approximately zero non-trivial programs have been written in C or C++ without memory management problems and/or vulnerabilities.

That's an ignorant and wrong assertion, spoken with an incredible amount of confidence. Look up software verification. There are verifiers for C.

This is misleading. Formally verifying the behaviour of any large software is a really tall task, no matter what language they are written in.

Re: ATM NFC Hack

#37
post #29

Earlier quoted context omitted.

That's an ignorant and wrong assertion, spoken with an incredible amount of confidence. Look up software verification. There are verifiers for C.

This is misleading. Formally verifying the behaviour of any large software is a really tall task, no matter what language they are written in.

That's not what the parent comment asserted though.
Post reply on HN