Hacker News new | past | comments | ask | show | jobs | submit login

> red and green are some form of standard for secure/insecure notifications.

They are. If you look at photos that the military/government publishes of facilities, the secure stuff is always red, and the public stuff is always green (well, always is a strong word. It is occasionally black). (I was going to include such an image now but I can't seem to find a search term for it that will find what I want.)

I agree, it seems a little backwards, but I guess it's a piece of domain-specific knowledge you don't forget once you've acquired it.




Historical German KWF secure analog telephone, with example red "secure" and green "clear" buttons. http://www.cryptomuseum.com/crypto/ant/kwf/

The convention evolved early, when secure communications were rare. The US/NATO clearly marked the secure lines with bright red phones, since the major danger is sending something in plaintext rather than secure, while the reverse error is more harmless.

The green phones followed (since green is the complementary color of red), more out of cargo cult thinking than any usability purpose, which is why you'll still see a lot of black equipment (because the colour of the unsecured line is relatively unimportant.)

And now, we have a hand-me-down convention that contravenes one of our hard-wired conventions about colors: Green: Go, Proceed, Correct, Benign Red: Stop, Not permitted, Incorrect, Harmful.

It is odd, but much like the wrong sign on the electron, you get used to it.


Historical German KWF secure analog telephone, with example red "secure" and green "clear" buttons

I'm confused; the article you linked to consistently says it's the other way around:

  - The green and red buttons at the front are for switching to SECURE and CLEAR mode respectively

  - When the user presses the green button... The exchange then switches to encrypted mode

  - ... Press the green button on the phone to cause the exchange to switch to encrypted mode

  - In normal use... the call is not encrypted and the red LED, marked Klar (clear), lights up

  - In secure mode, the red ET button can be used to switch back to clear mode again

There are a number of comments here stating that the convention is red secure/green insecure, so I presume the article's author is incorrect.

Or is this a classic illustration of UI confusion?


Huh, good catch. Either the author mixed up the description, or the designer confused the standard. I just grabbed the first example at hand, but a quick googling should turn up some more devices.


Yes, it's the official color-coding. In the sidebar at the right side of the article about the phones, you can see a box showing bars in five colors that represent the different classification levels, with green being for everything that's unclassified. Red stands for Secret, but in this case, where it's just secure/non-secure, or actually: unclassified/classified, red is used for classified in general.


I agree, it seems a little backwards, but I guess it's a piece of domain-specific knowledge you don't forget once you've acquired it.

Thanks, I had absolutely no idea about this.

I guess red/caution makes sense if the thinking is "this is secure, be careful with it!"


I'm thinking of the red light in submarines during quiet time.


'We are going to RED alert'

There are endless procedures about handling classified information. You are dealing with state secrets, girding for war, and what have you. From the perspective of security, you are 'arming' your system when you go to secure mode. It is not the time to relax because you are 'safe' (safe from evesdropping), but a time to watch every word - the President has access to information that he should not share with many people who are cleared; you need to be cautious and circumspect. Red is entirely appropriate in that mindset. Secure is a burden, a huge responsibility.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: