From a7f0014a534949578403f3b9d175a985efd57ec9 Mon Sep 17 00:00:00 2001 From: Atemu Date: Tue, 4 May 2021 05:44:31 +0200 Subject: [PATCH] Command/Multicast: use proper hyphen MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit GHC was complaining about it possibly being a homoglyph: Command/Multicast.hs:111:36: error: warning: treating Unicode character as identifier character rather than as '-' symbol [-Wunicode-homoglyph] -- using a nice prime, namely 2521−1 but the sheer size of this ^ | 111 | -- using a nice prime, namely 2521−1 but the sheer size of this | ^ 1 warning generated. --- Command/Multicast.hs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Command/Multicast.hs b/Command/Multicast.hs index 8133e1e726..7d059cc194 100644 --- a/Command/Multicast.hs +++ b/Command/Multicast.hs @@ -108,7 +108,7 @@ genAddress = starting "gen-address" (ActionItemOther Nothing) (SeekInput []) $ d -- Except for on Windows XP, secp521r1 is supported on all -- platforms by uftp. DJB thinks it's pretty good compared -- with other NIST curves: "there's one standard NIST curve - -- using a nice prime, namely 2521−1 but the sheer size of this + -- using a nice prime, namely 2521-1 but the sheer size of this -- prime makes it much slower than NIST P-256" -- (http://blog.cr.yp.to/20140323-ecdsa.html) -- Since this key is only used to set up the block encryption,