⌈⌋ ⎇ branch:  freshcode


Check-in [f21257ed67]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Additional howto/comments on login page regarding `lock` field requiring proper password hash or OpenID handle.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: f21257ed67e3e1cfac1dd42a8a58682809b02b22
User & Date: mario 2017-01-31 18:43:47
Context
2017-06-12
23:11
Check for UTF-8 encoding mismatches before piping row to feed. Also: add `summary` field. check-in: de80c25858 user: mario tags: trunk
2017-01-31
18:43
Additional howto/comments on login page regarding `lock` field requiring proper password hash or OpenID handle. check-in: f21257ed67 user: mario tags: trunk
18:42
Recent updates to basic spam blacklist. check-in: 792720840e user: mario tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to page_login.php.

︙︙
80
81
82
83
84
85
86








87
88
89
90
91
92
93

       <br>
       <small>Write it down somewhere! And use "<u class=action>lock</u>" within the submit form to apply it.</small>
     </form>
    </p>
    </td>
    </tr>
    </table>








    


HTML;
}

// drop relevant session data








>
>
>
>
>
>
>
>








80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101

       <br>
       <small>Write it down somewhere! And use "<u class=action>lock</u>" within the submit form to apply it.</small>
     </form>
    </p>
    </td>
    </tr>
    </table>
    
    <p style="color:#bbb">Logins may fail if you specified a raw password
    instead of an hash for the `lock` field.  Don't worry, such plain text
    passwords will be reencrypted twice per day.  So please just try later. 
    -- If your login using an OpenID fails, please take care to add or
    remove the trailing `/` slash.  Matching is rather strict and doesn't
    check for IRL equivalence at the moment.  -- If everything else fails,
    please just send a mail to info@…</p>
    


HTML;
}

// drop relevant session data
︙︙