From: Adrian-Ken Rueegsegger <ken@codelabs.ch>
To: joe@perches.com
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
Adrian-Ken Rueegsegger <ken@codelabs.ch>
Subject: [PATCH] crypto: Fix dead links.
Date: Tue, 24 Feb 2009 23:22:26 +0100 [thread overview]
Message-ID: <1235514146-7554-1-git-send-email-ken@codelabs.ch> (raw)
In-Reply-To: <1235506239.2501.46.camel@localhost>
Signed-off-by: Adrian-Ken Rueegsegger <ken@codelabs.ch>
---
crypto/gf128mul.c | 2 +-
crypto/sha256_generic.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/crypto/gf128mul.c b/crypto/gf128mul.c
index ecbeaa1..a90d260 100644
--- a/crypto/gf128mul.c
+++ b/crypto/gf128mul.c
@@ -4,7 +4,7 @@
* Copyright (c) 2006, Rik Snel <rsnel@cube.dyndns.org>
*
* Based on Dr Brian Gladman's (GPL'd) work published at
- * http://fp.gladman.plus.com/cryptography_technology/index.htm
+ * http://gladman.plushost.co.uk/oldsite/cryptography_technology/index.php
* See the original copyright notice below.
*
* This program is free software; you can redistribute it and/or modify it
diff --git a/crypto/sha256_generic.c b/crypto/sha256_generic.c
index caa3542..6349d83 100644
--- a/crypto/sha256_generic.c
+++ b/crypto/sha256_generic.c
@@ -2,7 +2,7 @@
* Cryptographic API.
*
* SHA-256, as specified in
- * http://csrc.nist.gov/cryptval/shs/sha256-384-512.pdf
+ * http://csrc.nist.gov/groups/STM/cavp/documents/shs/sha256-384-512.pdf
*
* SHA-256 code by Jean-Luc Cooke <jlcooke@certainkey.com>.
*
--
1.5.4.3
next prev parent reply other threads:[~2009-02-24 22:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-24 20:10 List of 404 URLs in kernel .c and .h files Joe Perches
2009-02-24 21:23 ` Randy Dunlap
2009-02-24 21:38 ` Joe Perches
2009-02-25 8:30 ` Alex Chiang
2009-02-25 20:22 ` Martin Mares
2009-02-24 22:22 ` Adrian-Ken Rueegsegger [this message]
2009-03-07 10:45 ` [PATCH] crypto: Fix dead links Herbert Xu
2009-02-25 1:41 ` List of 404 URLs in kernel .c and .h files David Newall
2009-02-25 6:57 ` Sitsofe Wheeler
2009-02-25 9:24 ` David Newall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1235514146-7554-1-git-send-email-ken@codelabs.ch \
--to=ken@codelabs.ch \
--cc=joe@perches.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox