From 0c0bc3aed3b43274bc052b43f9a446f1e8ec69ef Mon Sep 17 00:00:00 2001 From: "Crystal.Sea" Date: Thu, 3 Sep 2020 21:24:48 +0800 Subject: [PATCH] Update MessageDigestPasswordEncoder.java --- .../maxkey/crypto/password/MessageDigestPasswordEncoder.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maxkey-core/src/main/java/org/maxkey/crypto/password/MessageDigestPasswordEncoder.java b/maxkey-core/src/main/java/org/maxkey/crypto/password/MessageDigestPasswordEncoder.java index 9e760406e..4a7eafba9 100644 --- a/maxkey-core/src/main/java/org/maxkey/crypto/password/MessageDigestPasswordEncoder.java +++ b/maxkey-core/src/main/java/org/maxkey/crypto/password/MessageDigestPasswordEncoder.java @@ -75,7 +75,7 @@ import java.util.Base64; * @author Luke Taylor * @author Rob Winch * @since 5.0 - * @deprecated Digest based password encoding is not considered secure. Instead use an + * deprecated Digest based password encoding is not considered secure. Instead use an * adaptive one way function like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or * SCryptPasswordEncoder. Even better use {@link DelegatingPasswordEncoder} which supports * password upgrades. There are no plans to remove this support. It is deprecated to indicate