Skip to content
This repository has been archived by the owner on Oct 2, 2019. It is now read-only.

Security section needs user interaction guidelines #179

Open
marcoscaceres opened this issue Jun 25, 2013 · 3 comments
Open

Security section needs user interaction guidelines #179

marcoscaceres opened this issue Jun 25, 2013 · 3 comments
Assignees
Milestone

Comments

@marcoscaceres
Copy link
Contributor

It would be good if the sec/priv section described some user interaction guidelines... like not exposing A-D buttons to the user - and perhaps some other things.

@ghost ghost assigned jplyle Jun 25, 2013
@marcoscaceres
Copy link
Contributor Author

assigning to @jplyle. Be great to have this for the next F2F.

@marcoscaceres
Copy link
Contributor Author

Wikipedia states that:

Present-day uses of the A, B, C and D keys on telephone networks are few, and exclusive to network control. For example, the A key is used on some networks to cycle through different carriers at will (thereby listening in on calls). Their use is probably prohibited by most carriers. The A, B, C and D tones are used in radio phone patch and repeater operations to allow, among other uses, control of the repeater while connected to an active phone line.

There is probably scope in the UI guidelines for the exclusion of A, B, C and D.

@marcoscaceres
Copy link
Contributor Author

Having said that, there may be some private telephony networks that make use of A-D...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants