Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Embedding the key pinentry say: "Open tomb: <keyname>.tomb.key" to set password #42

Closed
nignux opened this issue Aug 30, 2011 · 3 comments
Labels

Comments

@nignux
Copy link
Member

nignux commented Aug 30, 2011

In this way is confusing.
Must be something like: "Insert tomb steganography password"

@boyska
Copy link
Member

boyska commented Aug 31, 2011

Agree. Maybe jaromil has some ideas about this; I think he would like to move steganography support out of tomb

@jaromil
Copy link
Member

jaromil commented Aug 31, 2011

nope. bury/exhume can stay in tomb... the idea of undertaker is an auxiliary program to retrieve keys (so far...)

now you mention, it might make sense to move steg as a whole out, since it doesn't requires suid to be operated.

jaromil added a commit that referenced this issue Jan 17, 2012
merging boyska's branch to current master
changes some previous names of options:
--path --batch --poll

work in progress, refers to issues: #71 #70 #69 #58 #42 #27 #5
@boyska
Copy link
Member

boyska commented Jan 31, 2012

this seems to be fixed here. git blame says about 0de6541 as the commit fixing it, btw.

@boyska boyska closed this as completed Jan 31, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants