undefined | Better HN

0 pointswoodman9y ago0 comments

> ... whether added by the designer or by someone else.

Your exception seems to hing on the word designer. I'd describe the individual responsible placing the backdoor as the designer. So if you place a modified version of /usr/sbin/sshd, then you've designed the backdoor for that system. I see no redefinition.

0 comments

mordocai9y ago

Your post further up in the thread:

> Calling BO a backdoor is a major corruption of the word, as you loose the only word for describing intentionally weakened security - so that you may describe a thing which already has several more explicitly defining names: malware, trojan, dropper, etc.

Thinking in that context, it sounded like you were arguing further for the fact that backdoors should only be describing intentionally weakened security. Have you changed your mind about that?

woodmanOP9y ago

> Have you changed your mind about that?

No. Unlike a rootkit, context really matters in the case of a backdoor - not so much the implementation means. BO is no more a backdoor than vnc or sshd. Now if Dell decides to secretly package BO in their product line, then it is a backdoor.

> ...backdoors should only be describing intentionally weakened security.

I can't think of a backdoor that does not meet that description, do you have anything in mind?

j / k navigate · click thread line to collapse