<html>
<head>
<base href="https://bugs.webkit.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - htdigestparser fails out early when malformed entries are found"
href="https://bugs.webkit.org/show_bug.cgi?id=170055#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - htdigestparser fails out early when malformed entries are found"
href="https://bugs.webkit.org/show_bug.cgi?id=170055">bug 170055</a>
from <span class="vcard"><a class="email" href="mailto:lforschler@apple.com" title="Lucas Forschler <lforschler@apple.com>"> <span class="fn">Lucas Forschler</span></a>
</span></b>
<pre>(In reply to Lucas Forschler from <a href="show_bug.cgi?id=170055#c5">comment #5</a>)
<span class="quote">> This problem occurred when we moved to an updated database on the new DB
> server. Previously, I believe the malformed entries were not exported, or
> possibly there was some flaw that allowed them to pass through.
>
> As it currently works, we never finish parsing the entries. If you are lucky
> enough to have your credentials in the list before any malformed entry, then
> you can log in.
>
> One could argue the solution would be to clean up the database of any
> malformed entries... but that would not prevent a new one from being created.</span >
Actually, I misspoke. With the in place logic, if we run into a malformed entry, we simply bail out... no one can authenticate, as no entries are returned to validate.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>