|
Bugzilla – Full Text Bug Listing |
| Summary: | can't decrypt files with gpg | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Peter Poeml <poeml> |
| Component: | Security | Assignee: | Lukas Tinkl <ltinkl> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Minor | ||
| Priority: | P5 - None | CC: | coolo, nadvornik, security-team |
| Version: | Alpha 6 | ||
| Target Milestone: | --- | ||
| Hardware: | PowerPC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Peter Poeml
2007-07-24 06:30:36 UTC
reassigning to maintainer Did you already look into this, Lukas? I need some vacation. I'd like to be able to access hrworks again... I did but I'm unable to reproduce it... Which part? The file decryption part Peter, can you please try it again with strace -f and attach here the output? Preferably on beta2. http://download.opensuse.org/repositories/home:/ltinkl/openSUSE_Factory/ contains newest version of gpg2, can you please try out out to see if it fixes your problem? TIA Peter? Unfortunately, I had no opportunity to update the machine to something later than Alpha 6 yet. Peter, could you try at least strace? See comment 6. I took a short look and I have good news. It seems I already update the machine to Beta1, according to /etc/SuSE-release, and it turns out that decryption now works. "gpg -d foo.gpg" now results in transparently starting gpg-agent which in turn spawns pinentry-curses, and after entering the passphrase the decrypted file is output. Thus, it seems as if the bug is fixed since Beta1. It seems I can't use gpg anymore from vim like autocmd BufReadPost,FileReadPost *.gpg '[,']!gpg -d 2> /dev/null pinentry-curses is spawned here too, but it doesn't grab the pty as it seems. This worked with the previous gpg. I wonder if there is a way which allows using gpg like this again. Not sure if this a gpg bug. Feel free to close. I assume then this bug is dupe of #302323 which will be resolved shortly *** This bug has been marked as a duplicate of bug 302323 *** |