Context Navigation

Changes between Initial Version and Version 1 of Ticket #62954, comment 1

-                      initial
+                      v1
 I'm trying to figure out what would be a good patch for this.
 For password generation I assume that `password_hash` is the way to go here. But I wonder if this could not cause some backwards compatibility troubles, on how `post_password` is currently defined and made. Considering that this is a flaw, I assume that we thinking on a new option, must override any BC limitations, right? (I don't have much experience on how this has been approached historically)
+For password generation I assume that `password_hash` on the fly is the way to go here.
 Handling of the password could be in this form (I've picked part of this content, like the randomization, from a plugin snippet that does something similar).
 …
 {{{
 $pw = $_POST['post_tokenized_pass'];
 $hash = get_post_meta($post->ID, '_hashed_post_password', true);
+$hash = password_hash(the_post_password());
 if ($hash && password_verify($pw, $hash)) {
     $token = bin2hex(random_bytes(24));
 …
 So basically, with an access token approach, two potential issues come to my mind:
 - BC issues
+- BC potential issues?
 - Potential DB Performance issues