Closed liginity closed 3 years ago
Confirm this bug. Looks like when giving a wrong password, cryptoObj.subtle.decrypt
will try to continue instead of throwing a exception on Safari and Chrome.
Fix should be in this week.
Online demo has been updated, and you can try it again.
It is ok now with iPadOS 14 Safari and Chrome about the wrong_pass_message
.
I notice that the post empty password now has no encryption effect.
Technically, this is as expacted. If a user doesn't set a password, then we should think that user has no intention to encrypt it.
Issue
When wrong passwords are input, instead of showing the
wrong_pass_message
, thewrong_hash_message
comes out on iPadOS Safari and Chrome, and the content is just disordered code, when visiting posts on the demo website mhexo.github.io.Expected Behavior
wrong_pass_message
shows up.Actual Behavior
wrong_hash_message
shows up, and the content is just disordered code.Steps to Reproduce the Problem
wrong_hash_message
shows up.Specifications
iPadOS 14, Safari or Chrome.