hare

commit a6092178bc99b176fd427998f125ffcee8b97a3f
parent 8dc0d620d50128ddfb464835912aebab01ad09a0
Author: Alexey Yerin <yyp@disroot.org>
Date:   Tue, 11 May 2021 15:39:15 +0300

crypto/md5,sha1: fix sha256 and sha512 references

Going a submodule up is not supported, using an absolute reference
instead.

Diffstat:
M
crypto/md5/md5.ha
 | 
4
++--
M
crypto/sha1/sha1.ha
 | 
2
+-

2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/crypto/md5/md5.ha b/crypto/md5/md5.ha
@@ -22,8 +22,8 @@ type digest = struct {
 
 // Creates a [[hash::hash]] which computes a MD5 hash as defined in RFC 1321.
 // Note that MD5 is cryptographically broken and should not be used for secure
-// applications. Where possible, applications are encouraged to use [[sha256]]
-// or [[sha512]] instead.
+// applications. Where possible, applications are encouraged to use
+// [[crypto::sha256]] or [[crypto::sha512]] instead.
 export fn md5() *hash::hash = {
 	let md5 = alloc(digest {
 		hash = hash::hash {
diff --git a/crypto/sha1/sha1.ha b/crypto/sha1/sha1.ha
@@ -25,7 +25,7 @@ type digest = struct {
 
 // Creates a [[hash::hash]] which computes a SHA-1 hash. Note that this
 // alogorithm is no longer considered secure. Where possible, applications are
-// encouraged to use [[sha256]] or [[sha512]] instead.
+// encouraged to use [[crypto::sha256]] or [[crypto::sha512]] instead.
 export fn sha1() *hash::hash = {
 	let sha = alloc(digest {
 		hash = hash::hash {