Re: API documentation for Python GpgMe bindings?
Hello :) Bjoern Kahl writes: > I'd tried to play around with the (new) Python bindings announced just > a few days ago, but I am a bit lost. I am using Python-2.7 on MacOS > "El Captain", with Python-2.7, gpg2, gpgme (1.6.0_2) and the bindings > py27-pygpgme and pyme all installed using MacPorts. note that pygpgme is an entirely different project. > (Yes, that is not the newest gpgme-1.7.0 announced last week, the > announcement last week just made me aware of the fact that there > are Python binding at all.) Note that 'pyme' as available from MacPorts is likely the old pyme. You can grab and build the new 'pyme3' bindings from pypi, provided that you do have all the build dependencies. I'm not familiar with MacPorts, but that might help with that. (Despite the name, 'pyme3' also works with Python 2.7. Originally, it was only for Python 3, but we backported it. 'pyme3' was the working title, and it helps to differentiate between the old and the new binding.) > I know the C-library documentation of GpgMe found here: > https://www.gnupg.org/documentation/manuals/gpgme/ > > Is there a similar documentation for the Python bindings "pyme" (or > "pyme3")? No, unfortunately not at this point. > Looking at the C-library documentation and the help() output in the > Python interpreter for pyme and objects accessible from there, I fail > to see a clear mapping on how to call various functions. 'pyme3' has a high-level api with curated docstrings. Cheers, Justus signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: recording and retrieving "secrets" into gpg files
Hi Arbiel, Arbiel (gmx): > Hi Stephan > > The "Bash scripting" material, which I began reading, gave me some > valuable informations and I will go on reading it. > > On the other hand, I did not understand the aim of the material > concerning bash for gpg, as it deals with issues which I am quite > unaware of. Maybe, when I get more confident in gpg concepts, will I > understand its purpose. > > In fact, I wish to record "secrets" in gnome-keyrings, as seahorse does, > and I am looking for tutorials which explain how to do so with bash > scripts, which are the only "programs" I am able to write. Ah, ok, you were still with that, so it was sort of misunderstanding. For me it wasn't quite clear whether your new question really had anything to do with your old (storing secrets in gnome-keyrings), or whether (what I thought at last) it was a new one and generic. So I gave you two links, one for bash scripting in general, and the one related to gpg (as an example) for bash scripting concerning gpg. No, that file verification bash scripting hasn't anything to do with storing secrets in keyrings. I looked again but haven't found anything specific related to your question. Cheers, Stephan > Le 30/09/2016 à 17:30, Stephan Beck a écrit : >> Hi Arbiel, >> >> Arbiel (gmx): >>> Hi >>> >>> Thank you Andrew. >>> >>> In the material I've been ready lately, all examples are written in a >>> programming language and I only have abilities in bash scripting. >>> >>> Can somebody, please, direct me toward a url where they provide bash >>> scripting examples. >> [...] >> Bash scripting in general? >> http://bash-hackers.org >> >> related to gpg? For instance, >> https://github.com/Whonix/gpg-bash-lib >> >> Cheers, >> >> Stephan >> >> ___ >> Gnupg-users mailing list >> Gnupg-users@gnupg.org >> http://lists.gnupg.org/mailman/listinfo/gnupg-users >> > 0x4218732B.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Agent forwarding failure when the socketdir was autodeleted
Hi, Using GnuPG 2.1.15 I'm trying to SSH into a remote machine with OpenSSH 6.7 as described under: https://wiki.gnupg.org/AgentForwarding The problem is that the remote system uses systemd so /var/run/user/ exits and GnuPG will use it. But if I am not logged in or there is no gnupg process running. systemd autodeletes /var/run/user//gnupg this causes the remote forward of the Socket to fail because the directory for the socket does not exist and SSH won't create it. :-/ Any ideas how to solve this without requireing changes to the root configuration of the remote machine? I would happily update the wiki with a solution. Regards, Andre -- Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Why GnuPG encrypted file has no icon?
Hi, On Saturday 01 October 2016 04:10:03 Rohit P wrote: > When you encrypt multiple files in a folder, GnuPG encrypted files have no > icon. It is difficult to immediately identify which are the encrypted > files. If you are using Gpg4win you can try out our Beta of gpg4win-3.0 (See: https://wiki.gnupg.org/Gpg4win/Testversions ) There we added set up of file extensions and handling of files by "double click" for Windows. > Any specific reason why encrypted files have no icon? One problem was that the .pgp / .gpg / .asc extentions are pretty general. It could be Keys, signed data, detached signatures, etc.. so to bind them to an application the application would have to detect what a file is and handle it appropiately. This is done now by Kleopatra. Regards, Andre -- Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Terminology - certificate or key ?
On 03.10.2016, Werner Koch wrote: > We would call the left one a "normales Vorhangeschloss" (simple > padlock). But the middle one is known as a "Schappschloss" - referring > to the feature that you do not need a key to lock it. The left one is a modular padlock, and the one in the middle is an integrated padlock. According to one of my friends who is a native en_GB speaker. Not shure if this helps, though. I guess most languages simply use "padlock" for both types. Haengeschloss in German, hengelås in NO, hänglås (SE), hængelås (DK).. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Agent forwarding failure when the socketdir was autodeleted
On Tue 2016-10-04 08:03:06 -0400, Andre Heinecke wrote: > Using GnuPG 2.1.15 I'm trying to SSH into a remote machine with OpenSSH 6.7 > as > described under: > > https://wiki.gnupg.org/AgentForwarding > > The problem is that the remote system uses systemd so /var/run/user/ > exits and GnuPG will use it. > > But if I am not logged in or there is no gnupg process running. systemd > autodeletes /var/run/user//gnupg this causes the remote forward of the > Socket to fail because the directory for the socket does not exist and SSH > won't create it. :-/ If you're not logged in, then how does the remote forward work? aren't you actually still logged in (via ssh) as long as your remote forward is running? --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Agent forwarding failure when the socketdir was autodeleted
Hi, On Tuesday 04 October 2016 11:26:59 Daniel Kahn Gillmor wrote: > > But if I am not logged in or there is no gnupg process running. systemd > > autodeletes /var/run/user//gnupg this causes the remote forward of > > the > > Socket to fail because the directory for the socket does not exist and SSH > > won't create it. :-/ > > If you're not logged in, then how does the remote forward work? aren't > you actually still logged in (via ssh) as long as your remote forward is > running? Sorry for not formulating this better. You are of course right If I'm not logged in the remote forward is not working. That is not what I meant to say. The problem is, that when I disconnect the /run/.../gnupg dir is deleted and the next time I want to connect and ssh tries to set up the forwarding this will fail because the /run/.../gnupg directory in which the forwarded socket should be created does not exist. Warning: remote port forwarding failed for listen path /var/run/user//gnupg/S.gpg-agent My current workaround is to connect first and start dirmngr on the remote machine (to get the socketdir created and used). And then connect with ssh socket forwarding. This is a bit clunky to use. I've tried placing files in that folder, or to set up permissions to 000 for the gnupg folder (so that gnupg itself does not use it) but to no avail. It's still removed when disconnecting and the next connect will fail. Regards, Andre -- Andre Heinecke | ++49-541-335083-262 | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner signature.asc Description: This is a digitally signed message part. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Agent forwarding failure when the socketdir was autodeleted
Hi Andre-- On Tue 2016-10-04 14:49:00 -0400, Andre Heinecke wrote: > On Tuesday 04 October 2016 11:26:59 Daniel Kahn Gillmor wrote: >> > But if I am not logged in or there is no gnupg process running. systemd >> > autodeletes /var/run/user//gnupg this causes the remote forward of >> > the >> > Socket to fail because the directory for the socket does not exist and SSH >> > won't create it. :-/ >> >> If you're not logged in, then how does the remote forward work? aren't >> you actually still logged in (via ssh) as long as your remote forward is >> running? > > Sorry for not formulating this better. You are of course right If I'm not > logged in the remote forward is not working. > > That is not what I meant to say. The problem is, that when I disconnect the > /run/.../gnupg dir is deleted and the next time I want to connect and ssh > tries to set up the forwarding this will fail because the /run/.../gnupg > directory in which the forwarded socket should be created does not exist. so /run/user/ exists upon ssh connection, but /run/user//gnupg/ does not, and therefore sshd on the remote side of the pipe can't auto-create the remote socket -- is that the concern? > My current workaround is to connect first and start dirmngr on the remote > machine (to get the socketdir created and used). And then connect with ssh > socket forwarding. This is a bit clunky to use. agreed, that sounds clunky and annoying. I wonder whether ssh's remote socket forwarding ought to try to automatically create the parent directories if they don't already exist. This doesn't solve your problem in the near term if you can't update the remote host, but it seems like the right place to fix this problem. Maybe that's worth asking on openssh-unix-...@mindrot.org ? > I've tried placing files in that folder, or to set up permissions to 000 for > the gnupg folder (so that gnupg itself does not use it) but to no avail. It's > still removed when disconnecting and the next connect will fail. right, session termination (or machine reboot, etc) should clean up /run/user/ entirely -- that's part of the explicit goal of $XDG_RUNTIME_DIR, aiui. --dkg signature.asc Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Private Key Encryption
Hi Team, We are performing encryption and decryption process. We are using the SUSE Linux 11 SPS3 OS. We want to Encrypt and Sign the file using gpg encryption technique. As a Linux OS root user, we are able to generate keys and perform Encryption, Signing, Verification and Decryption perfectly and we are also able to list the generated keys. We want to use these keys in the SAP R/3 System. The administrator user for the SAP System is SIDADM. In our case it is SF2ADM. We switch the user from root to sf2adm and try to generate the keys using the command gpg --gen-key. But we are not able to enter the passphrase for the key. Instead we are getting the error message stating that "gpg: Cancelled by user" "gpg: Key generation canceled." Please find the attached screenshot of the same. We have tried the following : 1)Adding a new user home using the command addgnupghome 2)gpg-agent --daemon and setting the link to the requires S-gpg-agent in /tmp/ directory. 3)We thought the issue was because of terminal type to be set. We have tried setting GPG_TTY to $tty. But the issue has not been resolved yet. Could you please let us know what is the procedure to perform encryption and decryption using gpg technique on Linux OS without the root user( Using a different user) Thanks and Regards, Swetan G _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ The information contained in this transmission is confidential. It is intended solely for the use of the individual(s) or organization(s) to whom it is addressed. Any disclosure, copying or further distribution is not permitted unless such privilege is explicitly granted in writing by PCM, Inc. Furthermore, PCM, Inc. is not responsible for the proper and complete transmission of the substance of this communication, nor for any delay in its receipt. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
