Enable 'secure keyboard entry' in iterm2
By lazy... on November 02, 2010 21:37 (imported from Google Code)
What steps will reproduce the problem?
- type text, such as ssh-agent password
2.
3.
What is the expected output? What do you see instead?
No expected output
What version of the product are you using? On what operating system?
10.6.4
Please provide any additional information below.
It would be nice ( essential) to have Terminal's 'secure keyboard entry' for iTerm.
Otherwise, a nice piece of work!
P.S. Really, essential. Terminal's secure keyboard entry gives me a place to stand if i feel my system is compromised.
Activity
Comment 1 by gnach... on November 02, 2010 21:41
Here's a description of the feature:
I am not sure what you mean?
Terminal's 'Secure Text Entry' means the app turns on EnableSecureInputMode.
QUOTE
You can set up Terminal to allow secure keyboard entry. This prevents other applications on your computer or the network from detecting and recording what you type in Terminal. Before you turn this option on, make sure other applications on your own computer don't need this information.Or, more technically:
QUOTE
When secure event input mode is enabled, keyboard input goes only to the application with keyboard focus and is not echoed to other applications that might be using the event monitor target to watch keyboard input. The EditText and EditUnicodeText controls automatically enter secure input mode when a password control has focus. If your application implements its own password entry, you should enable secure event input while the user enters text.This is actually kind of a pain-in-the-ass, since it breaks a lot of Accessibility and automation tools, including disabling any globally-registered hotkeys (including Atlantis' own). If this is super-super critical to folks I will look into adding it after 0.9.8.1, but it will mean I have to disable some of the hotkey functionality whenever Secure Mode is on.
-
Comment 2 by lazy... on November 12, 2010 01:44
Frankly, it's super critical. iTerm needs to function as a terminal first IMO. that lack of secure input means that I can't run it in sysadmin situations. Until it has that, it's a toy, not to be insulting, because given that feature, it becomes finally, a Terminal.app replacement.
I've become quite interested in where that quote comes from by the way. What is the 'event monitor target'?
-
Comment 3 by lazy... on November 12, 2010 01:44
Frankly, it's super critical. iTerm needs to function as a terminal first IMO. that lack of secure input means that I can't run it in sysadmin situations. Until it has that, it's a toy, not to be insulting, because given that feature, it becomes finally, a Terminal.app replacement.
I've become quite interested in where that quote comes from by the way. What is the 'event monitor target'?
-
Comment 4 by lazy... on November 12, 2010 01:49
I can, with 100% assurance say that other applications DO NOT need my keystrokes in my terminal. Possibly you may have heard what you thought was a coyote, or howling dog just now. That actually was me, realizing the impact of what lack of "secure input mode" means. Please, this is quite important, I use my terminal for admin a lot. I'd prefer Iterm.
mentioned in commit d94c6a52