4 ms·

One problem I have with this is that its a massive security hole. Where does the output get stored? If its in an encrypted file, okay .. but if not: deal brea

by ibisum 12y ago

One problem I have with this is that its a massive security hole. Where does the output get stored? If its in an encrypted file, okay .. but if not: deal breaker.

interpol_p 12y ago
You can disable it system wide. But it also works on a per-app basis: if you don't want the UI state restored, then just quit the app with Cmd+Option+Q (instead of the regular Cmd+Q) and OS X will not save the application state.
- nnnnni 12y ago
  I wish that there would have been a setting in the program options ("Preferences"... I don't know why, but that word annoys me in this context) so that the user wouldn't always have to do cmd-opt-q. Maybe the best option would be to have a checkbox that swaps the behavior ("don't save the output unless I press cmd-opt-q"). THANKS for letting us know about cmd-opt-q! I'll have to start using that all the time since it does seem like a potential security hole.
  - interpol_p 12y ago
    You can disable window restoration system wide (System Preferences -> General -> "Close windows when quitting an app"). So you don't have to use the shortcut at all in that case. Personally I prefer getting used to using it on a case-by-case basis. For example, when I leave work I tend to quit most apps on my laptop with Cmd+Option+Q, so that when I get home they don't re-open with work and I can start working on personal projects.
    - nnnnni 12y ago
      I don't want to disable it system-wide -- just for the terminal! I'll just have to get used to cmd-opt-q.
      - redacted 12y ago
        defaults write com.apple.Terminal NSQuitAlwaysKeepsWindows -bool false or something similar ought to do the trick
acdha 12y ago
1. If you regularly have passwords, keys, PII, etc. in terminal windows, your workflow should change. 2. If you care about security in any way, you should be using FileVault rather than cargo-culting it into apps (there's no way for that "encrypted file" to be secure unless you have to type in a password every time you shut down the system). If you do that, anyone who can read that file has already compromised your account and there's no additional exposure from this.
- ibisum 12y ago
  >1. If you regularly have passwords, keys, PII, etc. in terminal windows, your workflow should change. Security is not just about passwords. Its about operational knowledge of procedures and habits at the console, too. Knowing that a certain command is always used, or some such operational administration occurs, definitely assists attack. >2. FileVault FileVault is not always available, nor is it always allowable. But history files are not only about password, as I said.

by ibisum 12y ago

One problem I have with this is that its a massive security hole. Where does the output get stored? If its in an encrypted file, okay .. but if not: deal breaker.

interpol_p 12y ago

You can disable it system wide. But it also works on a per-app basis: if you don't want the UI state restored, then just quit the app with Cmd+Option+Q (instead of the regular Cmd+Q) and OS X will not save the application state.

nnnnni 12y ago
I wish that there would have been a setting in the program options ("Preferences"... I don't know why, but that word annoys me in this context) so that the user wouldn't always have to do cmd-opt-q. Maybe the best option would be to have a checkbox that swaps the behavior ("don't save the output unless I press cmd-opt-q"). THANKS for letting us know about cmd-opt-q! I'll have to start using that all the time since it does seem like a potential security hole.
- interpol_p 12y ago
  You can disable window restoration system wide (System Preferences -> General -> "Close windows when quitting an app"). So you don't have to use the shortcut at all in that case. Personally I prefer getting used to using it on a case-by-case basis. For example, when I leave work I tend to quit most apps on my laptop with Cmd+Option+Q, so that when I get home they don't re-open with work and I can start working on personal projects.
  - nnnnni 12y ago
    I don't want to disable it system-wide -- just for the terminal! I'll just have to get used to cmd-opt-q.
    - redacted 12y ago
      defaults write com.apple.Terminal NSQuitAlwaysKeepsWindows -bool false or something similar ought to do the trick

acdha 12y ago

1. If you regularly have passwords, keys, PII, etc. in terminal windows, your workflow should change. 2. If you care about security in any way, you should be using FileVault rather than cargo-culting it into apps (there's no way for that "encrypted file" to be secure unless you have to type in a password every time you shut down the system). If you do that, anyone who can read that file has already compromised your account and there's no additional exposure from this.

ibisum 12y ago
>1. If you regularly have passwords, keys, PII, etc. in terminal windows, your workflow should change. Security is not just about passwords. Its about operational knowledge of procedures and habits at the console, too. Knowing that a certain command is always used, or some such operational administration occurs, definitely assists attack. >2. FileVault FileVault is not always available, nor is it always allowable. But history files are not only about password, as I said.