Home GnuPG

use https instead of cleartext http where possible
Concern Raised0df498e81fd3Unpublished

Unpublished Commit · Learn More

Not On Permanent Ref: This commit is not an ancestor of any permanent ref.

Description

use https instead of cleartext http where possible

The following domains all offer https, so use it:

  • creativecommons.org
  • cr.yp.to
  • cryptojedi.org
  • crypto.stanford.edu
  • csrc.nist.gov
  • donate.fsf.org
  • ed25519.cr.yp.to
  • eprint.iacr.org
  • git.savannah.gnu.org
  • gnu.org
  • graphics.stanford.edu
  • info.isl.ntt.co.jp
  • lists.gnu.org
  • lists.gnupg.org
  • people.csail.mit.edu
  • shiftleft.org
  • software.intel.com
  • tools.ietf.org
  • web.archive.org
  • web.cs.ucdavis.edu
  • www.calcurco.cat
  • www.columbia.edu
  • www.cs.tau.ac.il
  • www.cs.technion.ac.il
  • www.cs.ucdavis.edu
  • www.g10code.com
  • www.gnu.org
  • www.gnupg.org
  • www.ii.uib.no
  • www.intel.com
  • www.larc.usp.br
  • Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net>

Details

Auditors
werner
Provenance
dkgAuthored on May 14 2019, 7:53 PM
Parents
rC34e9306a66b4: tests/basic: mark CFB and CFB8 as stream block cipher modes
Branches
Unknown
Tags
Unknown
References
http-to-https

Event Timeline

No, that is excessive. If the license blurb will ever be change this can be done but not just because of changing a single letter.

This commit now has outstanding concerns.May 15 2019, 8:09 AM