From f7e4f2c0531cbad3e2ea4f3e5c1ad6d7d9d15070 Mon Sep 17 00:00:00 2001 From: Stefan Brand Date: Wed, 8 Nov 2017 08:30:13 +0100 Subject: [PATCH] Fixup URLs and openssl command in README --- README.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index c7acef5..854d86c 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ From the main view a token can be copied to the clipboard by tapping on it. From the pulley menu the token database can be exported to a file for backup purposes. The backup is a AES-256-CBC encrypted and Base64 encoded file containing a JSON-representation of the database. It can be decrypted with openssl using the following command: -openssl enc -d -a -aes-256-cbc -in +openssl enc -d -a -A -md md5 -aes-256-cbc -in if you need the information outside of SailOTP. @@ -25,8 +25,9 @@ It is also possible to generate tokens for SteamGuard (Steams TOTP-Variant for 2 ## Contact and Issues -If you find any bugs or want to suggest a feature, feel free to use Githubs -Issues feature or write an email to sailfish _AT_ seiichiro0185.org +If you find any bugs or want to suggest a feature, feel free to use Githubs Issues feature at +https://github.com/seiichiro0185/sailotp/issues +or write an email to sailfish _AT_ seiichiro0185.org ## License @@ -40,7 +41,7 @@ SailOTP uses the SHA-1 and HMAC-Implementation from SailOTP also uses the AES-Implementation from -https://github.com/mdp/gibberish-aes +https://code.google.com/archive/p/crypto-js/ The implementation of the TOTP-algorithm was inspired by: