Re: Removing all installed versions of GNUPG
://www.nabble.com/Removing-all-installed-versions-of-GNUPG-tp17464099p17507257.html Sent from the GnuPG - User mailing list archive at Nabble.com. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Removing all installed versions of GNUPG
Robert J. Hansen-3 wrote: giangios wrote: How can I remove all the installations? Depends a lot on your distribution of Linux. Shall I go to the build directory and type 'make uninstall'? That'll work for at least one of them. It would be more helpful if you were to let us know which distribution you're using, and where the gpg executables are located on your system. Removing GnuPG entirely from a Linux system is not recommended and is probably a bad idea. Many distributions use GnuPG to digitally sign their packages. Without GnuPG, you have no way of knowing if your packages are authentic. I have found out in the documentation this: 6.22) I just compiled GnuPG from source on my GNU/Linux RPM-based system and it's not working. Why? Many GNU/Linux distributions that are RPM-based will install a version of GnuPG as part of its standard installation, placing the binaries in the /usr/bin directory. Later, compiling and installing GnuPG from source other than from a source RPM won't normally overwrite these files, as the default location for placement of GnuPG binaries is in /usr/local/bin unless the '--prefix' switch is used during compile to specify an alternate location. Since the /usr/bin directory more than likely appears in your path before /usr/local/bin, the older RPM-version binaries will continue to be used when called since they were not replaced. To resolve this, uninstall the RPM-based version with 'rpm -e gnupg' before installing the binaries compiled from source. If dependency errors are displayed when attempting to uninstall the RPM (such as when Red Hat's up2date is also installed, which uses GnuPG), uninstall the RPM with 'rpm -e gnupg --nodeps' to force the uninstall. Any dependent files should be automatically replaced during the install of the compiled version. If the default /usr/local/bin directory is used, some packages such as SuSE's Yast Online Update may need to be configured to look for GnuPG binaries in the /usr/local/bin directory, or symlinks can be created in /usr/bin that point to the binaries located in /usr/local/bin. I have unistalled the 'preinstalled' gnupg and reinstalled the last version. When I run the command: rpm -q gnupg, now doesn't show any gnupg installation, but I can use it. Now I need to point the distribution packages (CENTOS 4.2) to use the last (and unique) installed GNUPG. If the default /usr/local/bin directory is used, some packages such as SuSE's Yast Online Update may need to be configured to look for GnuPG binaries in the /usr/local/bin directory, or symlinks can be created in /usr/bin that point to the binaries located in /usr/local/bin. What shall I do? I am not very familiar to configure servers. :-/ -- View this message in context: http://www.nabble.com/Removing-all-installed-versions-of-GNUPG-tp17464099p17485108.html Sent from the GnuPG - User mailing list archive at Nabble.com. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Removing all installed versions of GNUPG
giangios wrote: When I run the command: rpm -q gnupg, now doesn't show any gnupg installation, but I can use it. Right -- rpm only knows about packages you add via rpm packages, not about random things you compile from source. Now I need to point the distribution packages (CENTOS 4.2) to use the last (and unique) installed GNUPG. You should be building a gnupg rpm. What shall I do? I am not very familiar to configure servers. :-/ The only sane advice would be to undo what you have done and not attempt to replace core system components until you better understand the system you are working with. I would recommend reading up on building packages with rpm, if you really feel that you must have a newer gnupg version installed in your server(s). A few places to start might be: http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide http://docs.fedoraproject.org/drafts/rpm-guide-en/ http://www.rpm.org/max-rpm-snapshot/ -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Whenever you find yourself on the side of the majority, it is time to pause and reflect. -- Mark Twain pgpUUfu8dtwhj.pgp Description: PGP signature ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Removing all installed versions of GNUPG
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, Giangios. | 3 installations of GNUPG. I would follow the following procedure -- 1) I would carefully and politely (aka, politically) ~ research why there are three gpg's installed on ~ the server. 2) Then I would update the correctly standardly ~ installed version of gpg. 3) Then I would politely send out an email/memo to all ~ parties involved in the non-standard copies of gpg, ~ and inform them that ~ The latest version of gpg has been installed ~ on the server in [the standard library]. ~ Please contact [someone] about using the ~ latest version of gpg. This change will ~ happen on end of day Friday [2008/05/23]. ~ Please, use all of the politeness that you can in ~ this email/memo, because you want the users to ~ contact you voluntarily to make sure that they ~ are using the correct gpg. 4) Cron a script to run on [2008/08/23] to delete ~ the two wrong gpg directories. Optionally -- 5) In the cron'd script, create symbolic links from ~ the old directories to the new directories. Sidebar tech ref guidance -- ~ Copied from a web page -- ~ln -s [TARGET DIRECTORY OR FILE] ./[SHORTCUT] ~ ~For example: ~ ~ln -s /usr/local/apache/logs ./logs ~ ~This points a symbolic link ./logs to /usr/local/apache/logs ~ Symbolic links in some of the Unices can have their own overhead ~ (OS is picky about doing rm -r when a Symbolic link is ~ encountered). On the Unices, Symbolic Links work super effectively ~ for program execution, and data access. As everyone is probably aware (probably), on the Unices, all individual keyrings are stored in a .gpg directory under each user's /home/[user]/ directory. I point that out so that I can point out the central point... that updating a central version of gpg should be invisibly impactless to any and all users, once they correct the use of the different/alternate/deleted versions of gpg. Further comment -- I ran across a similar problem in Windows. 1) One was needed by Cygwin (Linux under Windows), 2) one was needed by my email program (Thunderbird), and 3) one was needed by a GPG file toolpack (GPG4Win) that I use regularly. I determined that it would be easier to - -- do the installation into the default location (which is ~ where the GPG4Windows looks), and then - -- Do the installation again into the location that my email ~ program looked for GPG, and lastly - -- build the gpg for Cygwin from source. Technical Yes, during my efforts, I found out that there is a Windows Environment variable (as well as a cygwin/Unices alias) that can be set for GPG to look in one location for the executables... not PATH, but another one, something like gpgpath... the gpg docs are really written from a Unix/Linux perspective, and should cover this in perfect detail for your Linux-viewpoint. Best of Luck. Let me know off-list if there is anything else that you want to ask me directly about this task. Peace, Barry Smith giangios wrote: | Hi to evrybody, | | I am not very familiar with linux and I have found out that GNUPG was | installed more than once on the server. There was already a preinstalled one | and trying to install and configure the last version I have realized that I | have now 3 installations of GNUPG. | | How can I remove all the installations? | | Shall I go to the build directory and type 'make uninstall'? | | This would work in the 2 I have installed (maybe), but what concerning the | preinstalled version. | | Could somebody explain me how to remove all the installations? | | Thanks - -- Barry Smith (2008-01-21 2048 no expire) bnsmith001 [at] gmail [dot] com Public Key ID : 0xBA649960 Key fingerprint : BAF9 A3F3 DF31 5038 1D72 442C 80E9 FF84 BA64 9960 If you can't find my key, tell me what keyserver to upload it to, or ask my to send it to you directly. Outgoing mail is certified Virus Free. Checked by Norton 360 All-In-One (http://www.symantec.com). Peace and Love! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkg8fssACgkQgOn/hLpkmWA/sQCfVtKO+Clpbhxdr71alRacj2Ke 368An00FHi3TdF0l+YzCjzHXxjk7udcP =quG4 -END PGP SIGNATURE- ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
Re: Removing all installed versions of GNUPG
giangios wrote: How can I remove all the installations? Depends a lot on your distribution of Linux. Shall I go to the build directory and type 'make uninstall'? That'll work for at least one of them. It would be more helpful if you were to let us know which distribution you're using, and where the gpg executables are located on your system. Removing GnuPG entirely from a Linux system is not recommended and is probably a bad idea. Many distributions use GnuPG to digitally sign their packages. Without GnuPG, you have no way of knowing if your packages are authentic. ___ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
