Skip to main content


       GnuPG tries to  be  a  very  flexible  implementation  of  the  OpenPGP
       standard. In particular, GnuPG implements many of the optional parts of
       the standard, such  as  the  SHA-512  hash,  and  the  ZLIB  and  BZIP2
       compression  algorithms.  It  is  important  to  be  aware that not all
       OpenPGP programs  implement  these  optional  algorithms  and  that  by
       forcing  their use via the --cipher-algo, --digest-algo, --cert-digest-
       algo, or --compress-algo options in GnuPG, it is possible to  create  a
       perfectly  valid  OpenPGP  message,  but one that cannot be read by the
       intended recipient.

       There are dozens of variations of OpenPGP programs available, and  each
       supports a slightly different subset of these optional algorithms.  For
       example, until recently, no (unhacked) version  of  PGP  supported  the
       BLOWFISH cipher algorithm. A message using BLOWFISH simply could not be
       read by a PGP  user.  By  default,  GnuPG  uses  the  standard  OpenPGP
       preferences  system  that  will  always  do  the right thing and create
       messages that are usable by all recipients, regardless of which OpenPGP
       program  they  use.  Only override this safe default if you really know
       what you are doing.

       If you absolutely must override the safe default, or if the preferences
       on  a  given  key  are  invalid for some reason, you are far better off
       using the --pgp6, --pgp7, or --pgp8 options. These options are safe  as
       they  do  not  force any particular algorithms in violation of OpenPGP,
       but rather reduce the available algorithms to a "PGP-safe" list.

Posted By Blogger to HDGEM at 2/14/2017 01:28:00 PM
Post a Comment

Popular posts from this blog

How to reset password of Jenkins

Reset password of JenkinsPrefer way, No securities were harmedSee also:
What is Jenkins' initial admin password

To reset it without disabling security if you're using matrix permissions (probably easily adaptable to other login methods): In config.xml, set disableSignup to false.Restart Jenkins.Go to the Jenkins web page and sign up with a new user.In config.xml, duplicate one of the <permission>hudson.model.Hudson.Administer:username</permission> lines and replace username with the new user.If it's a private server, set disableSignup back to true in config.xml.Restart Jenkins.Go to the Jenkins web page and log in as the new user.Reset the password of the original user.Log in as the original user. Optional cleanup: Delete the new user.Delete the temporary <permission> line in config.xml.
Alternative way:
ssh to the server, disable authentication, set the password via the Jenkins Web UI, then enable authentication.

How to Remove / Hide "Powered by Blogger" (Attribution Gadget)

Settings -> Template -> Edit HTML -> Jump to widget: choose Attribution1

Change it to:

<b:widget id='Attribution1' locked='false' mobile='no' title='' type='Attribution'/>

Go to Layout, remove Attribution1 widget.

To hide: Template -> Customize ->  Advanced -> Add CSS - Paste the following code  -> Apply to Blog:
#Attribution1 { display: none!important; }