News for hackers. Stuff that matters.
Re:“I Want to Know What Code Is Running Inside My Body” by belorn on Tuesday August 09, 2016 @07:06AM (#12253732)
Security by obscurity is in practice almost always a bad idea.

1# security by obscurity gives a false sense of security. Under no circumstance should obscurity be used as a deciding factor behind a management decision.

2# security by obscurity cost money and time, and should only be used when all real form of security measures has been implemented. Even the military are currently not always implementing multi-token authentication, ipsec and selinux. Instead of trusting that the medical deceive is safe behind two layers, a static password and a secret port, add a certificate and implement challenge and response.

3# the priority to implement security by obscurity should be far lower than all the real security technologies. When reading security reports by pen testers, its important to understand the difference between a verified code injection vulnerability and a system information disclosure. Fixing a remotely code injection bug is much more important than hiding the fact that a system is running a up-to-date stable version of Debian, yet many security guides and reports for pen-testing tools rarely priorities.

4# security by obscurity often has real cost in support, brittleness of the system, and debugging. There is still in 2016 firewalls that will permanent block any ip address that has sent a icmp package to them. The amount of work employees are spending to unblock customers that accidentally end up in the block list could be spent on making sure that the system is just that more perfect against the serious attackers who can afford to spend $50 to access a botnet for a few hours.

Re:“I Want to Know What Code Is Running Inside My Body” by TickleSteve on Tuesday August 09, 2016 @07:18AM (#12253766)
I agree with your numbered points, but not the conclusion that its always a bad idea.

Its common sense that I can't pick a lock if I cant find the lock.

This says nothing about the quality of the lock or what is behind the lock.

Re:“I Want to Know What Code Is Running Inside My Body” by belorn on Tuesday August 09, 2016 @08:15AM (#12253982)
Almost never. I know where the bank is, I know where the door to the bank is, but that should not make it easy to break into the bank. However, a gold storage might want to keep the location hidden, as they should have already implemented all the security procedures of a bank plus extra.

Spending time on security by obscurity should be a job for the small minority of people who already done everything else, and then only if there is a cost-benefit analyze that show cost of the obscurity to be less than the calculated gains.

Re:“I Want to Know What Code Is Running Inside My Body” by TickleSteve on Tuesday August 09, 2016 @09:54AM (#12254473)
Order-of-implementation is entirely a project management issue. This does not affect quality of the final design

These types of products are entirely designed up front and analysed before any code is written so the implementation order is irrelevant.

Re:“I Want to Know What Code Is Running Inside My Body” by hx87 on Tuesday August 09, 2016 @12:23PM (#12255691)
If I make a lock for myself, then it makes sense to keep it hidden. If I'm buying a lock from someone else, I'd like to know where it is, so it makes less sense to keep it hidden, at least from me and my agents.