[opensuse] KGPG : Serious fault
TW : have installed : kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch ...... Decryption : upon entering password , error message appears saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears entire file in Decrypted form ! This is alarming and dangerous . Carlos , please , any ideas ? thanks ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2018 01:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
Carlos , please , any ideas ?
thanks
What is it that you are decrypting? A file? -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/18 01:23, John Andersen wrote:
On 06/01/2018 01:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
Carlos , please , any ideas ?
thanks
What is it that you are decrypting? A file?
Yes : a Text file ........ thank you ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/18 01:23, John Andersen wrote:
On 06/01/2018 01:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
Carlos , please , any ideas ?
thanks
What is it that you are decrypting? A file?
Yes : a Text file
........
This AM i have uninstalled kgpg-18.04.1-1.1.x86_64 & re-installed the previous kgpg-17.12.3-1.1.x86_64.rpm Unhappily the error persists : Decryption : upon entering password , error message appears saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears entire text file in Decrypted Plain Text ........ My Desktop Environment is XFCE - What might be the trouble - Malware / Trojan ?? What to do please ? ...... regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text
Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/18 14:48, Aaron Digulla wrote:
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all.
- thank you kindly : yes , had a look , is IS Encrypted regards ellan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On June 2, 2018 4:55:08 AM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 02/06/18 14:48, Aaron Digulla wrote:
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all.
- thank you kindly : yes , had a look , is IS Encrypted
regards
ellan
Serious fault seems to boil down to an erroneous error message. FTR I don't see this here. Encryption and decryption both work. Some software has taken to throwing warnings when weak keys were used (1024bits). My tests were run with much stronger keys. But I don't remember seeing such warnings from kgpg. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 02 Jun 2018 07:45:42 -0700 John Andersen <jsamyth@gmail.com> wrote:
On June 2, 2018 4:55:08 AM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 02/06/18 14:48, Aaron Digulla wrote:
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all.
- thank you kindly : yes , had a look , is IS Encrypted
regards
ellan
Serious fault seems to boil down to an erroneous error message.
Well it might be an erroneous error message, or it might be an indication that the message might have been tampered with (was it MDC or something missing?) Sorry I don't know enough to be sure.
FTR I don't see this here. Encryption and decryption both work.
Some software has taken to throwing warnings when weak keys were used (1024bits). My tests were run with much stronger keys. But I don't remember seeing such warnings from kgpg.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 02/06/18 17:45, John Andersen wrote:
On June 2, 2018 4:55:08 AM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 02/06/18 14:48, Aaron Digulla wrote:
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all. - thank you kindly : yes , had a look , is IS Encrypted
regards
ellan
Serious fault seems to boil down to an erroneous error message.
FTR I don't see this here. Encryption and decryption both work.
Some software has taken to throwing warnings when weak keys were used (1024bits). My tests were run with much stronger keys. But I don't remember seeing such warnings from kgpg.
- thank you kindly . - my key is , i believe , a strong one Team-Spokesperson kindly suggested that 'zypper dup' might fix probs : will do my weekly zypper dup on Sunday : keeping fingers crossed . ......... regards ellan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 18:29, ellanios82 wrote:
On 02/06/18 17:45, John Andersen wrote:
On June 2, 2018 4:55:08 AM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 02/06/18 14:48, Aaron Digulla wrote:
On 06/02/18 10:55, ellanios82 wrote:
Unhappily the error persists :
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire text file in Decrypted Plain Text Try to open the (supposedly) "encrypted" file in a text editor. Maybe it's really not encrypted at all. - thank you kindly : yes , had a look , is IS Encrypted
regards
ellan
Serious fault seems to boil down to an erroneous error message.
FTR I don't see this here. Encryption and decryption both work.
Some software has taken to throwing warnings when weak keys were used (1024bits). My tests were run with much stronger keys. But I don't remember seeing such warnings from kgpg.
- thank you kindly .
- my key is , i believe , a strong one
Team-Spokesperson kindly suggested that 'zypper dup'
might fix probs : will do my weekly zypper dup on Sunday : keeping fingers crossed .
Have you tried other applications to decipher the file? KGPG is not the only one. For plain text files I found that emacs is one of the best: emacs encrypted_text_file.gpg it asks for the password and opens it, never saving an open copy on disk. The "gpg" extension on the file name is important, emacs uses it to know it has to act in a particular way. And no, I don't really like emacs, but this is well done. Probably "vi" does something similar, I don't know. As your desktop environment is XFCE, it is perhaps easier to use Gnome tools. (side note: I just found out the Whisker Menu is configurable, and that pressing '#' you get man pages). The bad news is that they display on a terminal). Ok, settings, Session and startup, advanced tab. Make sure that "Launch Gnome services on startup is enabled". Also, you might want to experiment with "Launch KDE services on startup", if you want to use KGPG. Kleopatra is associated with it, if I remember correctly. In Gnome, the tool is "seahorse". Its purpose is not to handle text files, but to manage keys. Now that I remember, there were problems in XFCE desktop on how to handle "remembering" keys. This was supposed to be handled by a gnome service, but this one stopped caching pgp keys around Leap 42.2. Maybe does not apply to TW. Double click on an encrypted file.gpg inside Thunar produces a deciphered copy. For just handling keys, Thunderbird has a very good handler. And then, there are of course the command line tools, gpg and others. Not so comfortable, but they do just what you ask them to do ;-) All of the above I tested at writing time with Leap 42.3. There can be differences with TW. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 02/06/18 21:25, Carlos E. R. wrote:
Have you tried other applications to decipher the file? KGPG is not the only one.
Gee Carlos : thanks a lot : going to take me time to digest just some of this . cheers ....... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-02 20:53, ellanios82 wrote:
On 02/06/18 21:25, Carlos E. R. wrote:
Have you tried other applications to decipher the file? KGPG is not the only one.
Gee Carlos : thanks a lot : going to take me time to digest just some of this .
I had read your post yesterday but I stayed away because I do not use KGPG nor TW, so I read what other people said. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/02/2018 11:56 AM, Carlos E. R. wrote:
I had read your post yesterday but I stayed away because I do not use KGPG nor TW, so I read what other people said.
But you also suggested totally switching tools to Emacs, switching to Gnome, then throwing thunderbird into the mix. All this to decrypt an encrypted file, which apparently does work but throws an erroneous message. Seems a long way to go. But at least you didn't suggest switching distros and buying a new computer, so there's that. -- After all is said and done, more is said than done.
On 2018-06-02 21:07, John Andersen wrote:
On 06/02/2018 11:56 AM, Carlos E. R. wrote:
I had read your post yesterday but I stayed away because I do not use KGPG nor TW, so I read what other people said.
But you also suggested totally switching tools to Emacs, switching to Gnome, then throwing thunderbird into the mix.
All this to decrypt an encrypted file, which apparently does work but throws an erroneous message.
Seems a long way to go. But at least you didn't suggest switching distros and buying a new computer, so there's that.
I gave ideas if one tool fails, even it temporarily. No, I did not suggest switching to gnome. He uses XFCE, and this loads and uses Gtk and Gnome tool chains. It thus makes sense to also use some Gnome apps (not the desktop). Less load than using KDE tools - although I also like and use some KDE tools. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
Op zaterdag 2 juni 2018 21:07:46 CEST schreef John Andersen:
On 06/02/2018 11:56 AM, Carlos E. R. wrote:
I had read your post yesterday but I stayed away because I do not use KGPG nor TW, so I read what other people said.
But you also suggested totally switching tools to Emacs, switching to Gnome, then throwing thunderbird into the mix.
All this to decrypt an encrypted file, which apparently does work but throws an erroneous message.
Seems a long way to go. But at least you didn't suggest switching distros and buying a new computer, so there's that. Why this negative and cynical approach to shared knowledge? You may be superiour but here's a post that can be referenced to. My 2 cents.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zaterdag 2 juni 2018 20:53:29 CEST schreef ellanios82:
On 02/06/18 21:25, Carlos E. R. wrote:
Have you tried other applications to decipher the file? KGPG is not the only one. Gee Carlos : thanks a lot : going to take me time to digest just some of this .
Thanks, Carlos. Wiki worthy, I'd say. It would help a lot of people.
cheers
.......
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-03 00:31, Knurpht @ openSUSE wrote:
Op zaterdag 2 juni 2018 20:53:29 CEST schreef ellanios82:
On 02/06/18 21:25, Carlos E. R. wrote:
Have you tried other applications to decipher the file? KGPG is not the only one. Gee Carlos : thanks a lot : going to take me time to digest just some of this .
Thanks, Carlos. Wiki worthy, I'd say. It would help a lot of people.
Huh, I don't know. There is a lot of info I do not know much about. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 02/06/18 20:25, Carlos E. R. wrote:
(side note: I just found out the Whisker Menu is configurable, and that pressing '#' you get man pages). The bad news is that they display on a terminal).
Oh, that is a great tip! Thank you! -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 06/01/2018 03:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have pinentry pinentry-gtk2 pinentry-qt4 If you are using one that doesn't correspond to your desktop, it may actually be passing the password correctly to decrypt, but no providing the desktop specific exit code thus generating the failure dialog. I've seen cases where the correct pinentry is a loose dependency, so if you installed a desktop by other than choosing the whole pattern, you may be in this boat. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/06/18 17:43, David C. Rankin wrote:
On 06/01/2018 03:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have
pinentry pinentry-gtk2 pinentry-qt4
If you are using one that doesn't correspond to your desktop, it may actually be passing the password correctly to decrypt, but no providing the desktop specific exit code thus generating the failure dialog. I've seen cases where the correct pinentry is a loose dependency, so if you installed a desktop by other than choosing the whole pattern, you may be in this boat.
- very many thanks : guess i'm in that boat : - have just installed the qt5 & gnome flavors and now have installed : pinentry-qt5-1.1.0-2.1.x86_64 pinentry-gtk2-1.1.0-2.1.x86_64 pinentry-gnome3-1.1.0-2.1.x86_64 pinentry-1.1.0-2.1.x86_64 ..... thank you so much ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/06/18 17:43, David C. Rankin wrote:
On 06/01/2018 03:51 PM, ellanios82 wrote:
TW : have installed :
kgpg-18.04.1-1.1.x86_64 kgpg-lang-18.04.1-1.1.noarch
......
Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form !
This is alarming and dangerous .
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have
pinentry pinentry-gtk2 pinentry-qt4
If you are using one that doesn't correspond to your desktop, it may actually be passing the password correctly to decrypt, but no providing the desktop specific exit code thus generating the failure dialog. I've seen cases where the correct pinentry is a loose dependency, so if you installed a desktop by other than choosing the whole pattern, you may be in this boat.
- very many thanks : guess i'm in that boat : - have just installed the qt5 & gnome flavors and now have installed : pinentry-qt5-1.1.0-2.1.x86_64 pinentry-gtk2-1.1.0-2.1.x86_64 pinentry-gnome3-1.1.0-2.1.x86_64 pinentry-1.1.0-2.1.x86_64 ..... Have just done a "zypper dup" : sadly the error persists :( ... many thanks regards ... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 03/06/18 10:43 AM, David C. Rankin wrote:
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have
pinentry pinentry-gtk2 pinentry-qt4
Well DUH! /usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5 If that doesn't match,the code for running kde drops though to try to use "pinentry-qt" but # which pinentry-qt which: no pinentry-qt in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games) You could, of course link pinetry-qt to pinetry-qt4 Hmm. I suppose you could recode it to check for either 4 or 5 .... Perhaps this should be a bug report, but isn't that up to the TW or "15" people? I'm only 4running 42.3 so I don't think they will listen to me. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Op zondag 3 juni 2018 20:14:39 CEST schreef Anton Aylward:
On 03/06/18 10:43 AM, David C. Rankin wrote:
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have
pinentry pinentry-gtk2 pinentry-qt4
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5
If that doesn't match,the code for running kde drops though to try to use "pinentry-qt" but
# which pinentry-qt which: no pinentry-qt in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr /bin/X11:/usr/games)
You could, of course link pinetry-qt to pinetry-qt4
Hmm. I suppose you could recode it to check for either 4 or 5 ....
Perhaps this should be a bug report, but isn't that up to the TW or "15" people? I'm only 4running 42.3 so I don't think they will listen to me. Of course report a bug, 42.3 is still maintained and supported, it might even be that the bug is in Leap 15 and TW as well.
-- Gertjan Lettink a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-03 20:14, Anton Aylward wrote:
On 03/06/18 10:43 AM, David C. Rankin wrote:
There may be a mismatch in your pinentry package, You have 3 (maybe 4) options. On 42.3 you have
pinentry pinentry-gtk2 pinentry-qt4
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5
I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time. [Ah, it is pinentry-gtk2] I use gpg-agent: root \_ /usr/bin/X :0 -seat seat0 -auth /run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch root \_ lightdm --session-child 12 19 cer \_ /usr/bin/ck-launch-session /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display --write cer \_ /bin/sh /etc/xdg/xfce4/xinitrc -- /etc/X11/xinit/xserverrc cer \_ /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/cer/.gnupg/agent.info-Telcontar:0 /home/cer/.xinitrc cer \_ /usr/bin/gpg-agent --sh --daemon --keep-display --write-env-file /home/cer/.gnupg/agent.info-Telcontar:0 /home/cer/.xinitrc cer \_ xfce4-session In Session and start up, tab Application Autostart, I have marked: "Certificate and Key Storage (Gnome Keyring: PKCS#11 Component)" "SSH Key Agent (GNOME Keyring: SSH Agent)" "Seahorse Agent (Remember GPG passphrases)" (I think it doesn't work :-?) "Secret Storage Service (GNOME Keyring: Secret Service)". I have to create a new user and find out what is started there. I also see "KDEConnect daemon", which I disable instantly. I had a suspicion it was there. On a new virtual machine, created under 15 beta, I have: "Certificate and Key Storage (Gnome Keyring: PKCS#11 Component)" "Secret Storage Service (GNOME Keyring: Secret Service)" "SSH Key Agent (GNOME Keyring: SSH Agent)" But I haven't created a PGP key there yet, nor used it. Let me see... Menu, Accessories, Passwords and Keys. It opens Seahorse. File/New, then PGP Key. Fine, that was trivial. Now, create a sample encrypted file using "emacs sample.gpg". Oh, emacs is not installed. Do it. Grumble... no internet in VB. Change. Grumble. Reboot. Got it. Create sample.gpg file with emacs - it is using symmetric encryption (I don't remember if this is what I want). Well, the key is cached for reading, but is requested twice for writing. This is different. The key dialog is not identified, but I see that pinentry-gtk-2 is running, was started a minute ago. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5 I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time.
This can also byte you if you do a minimal X install and then install Tbird/enigmail. In this case there is no pinentry dependency for Tbird/enigmail and when you attempt to reply to a signed e-mail, you lock one core at 100% - until you kill Tbird. I have worked around it by just hunting down the right pinentry (generally pinentry-gtk2), but this is a problem that should be fixed going forward. I know it has been around since at least 13.1. -- David C. Rankin, J.D.,P.E.
On 06/03/2018 07:56 PM, David C. Rankin wrote:
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5 I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time.
This can also byte you if you do a minimal X install and then install Tbird/enigmail. In this case there is no pinentry dependency for Tbird/enigmail and when you attempt to reply to a signed e-mail, you lock one core at 100% - until you kill Tbird.
I have worked around it by just hunting down the right pinentry (generally pinentry-gtk2), but this is a problem that should be fixed going forward. I know it has been around since at least 13.1.
But can't we assume that some form of Pin Entry did appear, because the OP stated that it did in fact decrypt the file, and showed it to be decrypted in spite of the error message? Are we not Up the wrong tree barking? (again). -- After all is said and done, more is said than done.
On 04/06/18 06:04, John Andersen wrote:
On 06/03/2018 07:56 PM, David C. Rankin wrote:
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a problem. See line 47. Change that 4 to 5 I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time.
This can also byte you if you do a minimal X install and then install Tbird/enigmail. In this case there is no pinentry dependency for Tbird/enigmail and when you attempt to reply to a signed e-mail, you lock one core at 100% - until you kill Tbird.
I have worked around it by just hunting down the right pinentry (generally pinentry-gtk2), but this is a problem that should be fixed going forward. I know it has been around since at least 13.1.
But can't we assume that some form of Pin Entry did appear, because the OP stated that it did in fact decrypt the file, and showed it to be decrypted in spite of the error message?
Are we not Up the wrong tree barking? (again).
- me , OP : using XFCE on Tumbleweed : "Decryption : upon entering password , error message appears saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears entire file in Decrypted form in PLAIN TEXT ! This is alarming and dangerous ." ....... thank you regards -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On June 3, 2018 11:17:40 PM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 06/03/2018 07:56 PM, David C. Rankin wrote:
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a
See line 47. Change that 4 to 5 I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time.
This can also byte you if you do a minimal X install and then install Tbird/enigmail. In this case there is no pinentry dependency for Tbird/enigmail and when you attempt to reply to a signed e-mail, you lock one core at 100% - until you kill Tbird.
I have worked around it by just hunting down the right pinentry (generally pinentry-gtk2), but this is a problem that should be fixed going forward. I know it has been around since at least 13.1.
But can't we assume that some form of Pin Entry did appear, because
On 04/06/18 06:04, John Andersen wrote: problem. the OP
stated that it did in fact decrypt the file, and showed it to be decrypted in spite of the error message?
Are we not Up the wrong tree barking? (again).
- me , OP : using XFCE on Tumbleweed :
"Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form in PLAIN TEXT !
This is alarming and dangerous ."
.......
thank you
regards
So we don't have a pinentry problem. You were asked for and supplied a password. Nor was it dangerous. You did supply the correct password, and it properly decrypted the file. If you could Key in any random password, or none at all, THAT might be dangerous. Alarming, perhaps. Clearly you were alarmed. Now that you know that the only failure was a bogus error message, I rather suspect it's a lot less alarming. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 04/06/18 11:01, John Andersen wrote:
On June 3, 2018 11:17:40 PM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 06/03/2018 07:56 PM, David C. Rankin wrote:
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
Well DUH!
/usrbin/pinrentry is a script. Therein is code to detect what desktop you are using. If it is looking for KDE4 and you are using KDE5 then you have a
See line 47. Change that 4 to 5 I see XFCE is not listed, either. I see a pin-entry window when I type the passphrase, but I didn't pay much attention. I'll see next time. This can also byte you if you do a minimal X install and then install Tbird/enigmail. In this case there is no pinentry dependency for Tbird/enigmail and when you attempt to reply to a signed e-mail, you lock one core at 100% - until you kill Tbird.
I have worked around it by just hunting down the right pinentry (generally pinentry-gtk2), but this is a problem that should be fixed going forward. I know it has been around since at least 13.1.
But can't we assume that some form of Pin Entry did appear, because
On 04/06/18 06:04, John Andersen wrote: problem. the OP
stated that it did in fact decrypt the file, and showed it to be decrypted in spite of the error message?
Are we not Up the wrong tree barking? (again).
- me , OP : using XFCE on Tumbleweed :
"Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form in PLAIN TEXT !
This is alarming and dangerous ."
.......
thank you
regards So we don't have a pinentry problem. You were asked for and supplied a password.
Nor was it dangerous. You did supply the correct password, and it properly decrypted the file. If you could Key in any random password, or none at all, THAT might be dangerous.
Alarming, perhaps.
Clearly you were alarmed. Now that you know that the only failure was a bogus error message, I rather suspect it's a lot less alarming. - thank you , thank you ......
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-04 10:01, John Andersen wrote:
On June 3, 2018 11:17:40 PM PDT, ellanios82 <ellanios82@gmail.com> wrote:
On 04/06/18 06:04, John Andersen wrote:
On 06/03/2018 07:56 PM, David C. Rankin wrote:
On 06/03/2018 03:50 PM, Carlos E. R. wrote:
But can't we assume that some form of Pin Entry did appear, because the OP stated that it did in fact decrypt the file, and showed it to be decrypted in spite of the error message?
Are we not Up the wrong tree barking? (again).
- me , OP : using XFCE on Tumbleweed :
"Decryption : upon entering password , error message appears
saying "Decryption failed" , but , there is a tiny box for "Details" : upon opening details , full-page , there appears
entire file in Decrypted form in PLAIN TEXT !
This is alarming and dangerous ."
So we don't have a pinentry problem. You were asked for and supplied a password.
Nor was it dangerous. You did supply the correct password, and it properly decrypted the file. If you could Key in any random password, or none at all, THAT might be dangerous.
Alarming, perhaps.
Clearly you were alarmed. Now that you know that the only failure was a bogus error message, I rather suspect it's a lot less alarming.
No, it is indeed dangerous. kgpg produced an error, saying "decryption failed", but left a decrypted copy of the file in the directory. This is dangerous: the user thinks his data is still kept secret, but it is not. It is open. A thief stealing the disk would be able to read the secret file. This is a kgpg bug. If the purpose is to read plain text files, I still say to use instead emacs to read them, because it does not generate a deciphered file, but reads it in memory only. Or find another tool to view protected files in memory. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/04/2018 02:11 AM, Carlos E. R. wrote:
No, it is indeed dangerous.
kgpg produced an error, saying "decryption failed", but left a decrypted copy of the file in the directory. This is dangerous: the user thinks his data is still kept secret, but it is not. It is open. A thief stealing the disk would be able to read the secret file.
This is a kgpg bug.
Nobody is arguing that it isn't a bug. The user asked for a decrypted file. The user got one. Sending them to that monstrously large and bloated EMACs which does NOT create a file (which is what the user asked for) is counter productive. Using a 16 Inch Naval Battleship Gun to swat a fly, and then MISSING the target completely. -- After all is said and done, more is said than done.
On 2018-06-05 03:14, John Andersen wrote:
On 06/04/2018 02:11 AM, Carlos E. R. wrote:
No, it is indeed dangerous.
kgpg produced an error, saying "decryption failed", but left a decrypted copy of the file in the directory. This is dangerous: the user thinks his data is still kept secret, but it is not. It is open. A thief stealing the disk would be able to read the secret file.
This is a kgpg bug.
Nobody is arguing that it isn't a bug. The user asked for a decrypted file. The user got one.
Sending them to that monstrously large and bloated EMACs which does NOT create a file (which is what the user asked for) is counter productive.
Using a 16 Inch Naval Battleship Gun to swat a fly, and then MISSING the target completely.
You don't like emacs? Me neither. Then find us some tool other that deciphers a text file in *memory*. I found none. So, I swallow my dislike of emacs and use it. The alternative is windows. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 05/06/18 12:42, Carlos E. R. wrote:
So, I swallow my dislike of emacs and use it.
The alternative is windows.
No, there's no escape. Emacs runs on Windows, too. ;-) -- Liam Proven - Technical Writer, SUSE Linux s.r.o. Corso II, Křižíkova 148/34, 186-00 Praha 8 - Karlín, Czechia Email: lproven@suse.com - Office telephone: +420 284 241 084 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2018-06-05 13:00, Liam Proven wrote:
On 05/06/18 12:42, Carlos E. R. wrote:
So, I swallow my dislike of emacs and use it.
The alternative is windows.
No, there's no escape. Emacs runs on Windows, too. ;-)
LOL But I meant that in Windows there are several editors that can display and edit an encoded file working on memory only, without creating a deciphered file, which is dangerous. Even if the deciphered file is erased after working on it, there remains copies on deleted sectors on the disk, so if an attacker get access to the disk, it can also read the secret document in plain text. Probably. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
On 06/05/2018 03:42 AM, Carlos E. R. wrote:
You don't like emacs? Me neither. Then find us some tool other that deciphers a text file in *memory*.
I am specifically NOT going to do that. The OP did not want decipher into memory. An output file was desired. Stop substituting your requirements for someone else's. -- After all is said and done, more is said than done.
On 2018-06-05 18:41, John Andersen wrote:
On 06/05/2018 03:42 AM, Carlos E. R. wrote:
You don't like emacs? Me neither. Then find us some tool other that deciphers a text file in *memory*.
I am specifically NOT going to do that.
The OP did not want decipher into memory. An output file was desired. Stop substituting your requirements for someone else's.
Opinion noted. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)
participants (9)
-
Aaron Digulla -
Anton Aylward -
Carlos E. R. -
Dave Howorth -
David C. Rankin -
ellanios82 -
John Andersen -
Knurpht ＠ openSUSE -
Liam Proven