Message120341
| Author |
r.david.murray |
| Recipients |
eric.araujo, jelie, pitrou, r.david.murray |
| Date |
2010年11月03日.19:32:20 |
| SpamBayes Score |
6.6696402e-06 |
| Marked as misclassified |
No |
| Message-id |
<1288812744.25.0.755654545118.issue10284@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
What I meant by saying that the spec was broken is that the user is going to be typing the password at a keyboard. The keyboard will generate scan codes. Those scan codes will get interpreted through a system-specific chain of processes until some bytes or some unicode characters are generated. What's to say that the password typed on the keyboard where the password is set up is going to be a binary match for the password entered on the keyboard used for authentication?
Which doesn't change the fact that if the spec calls for binary, nttplib should support binary. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年11月03日 19:32:24 | r.david.murray | set | recipients:
+ r.david.murray, pitrou, eric.araujo, jelie |
| 2010年11月03日 19:32:24 | r.david.murray | set | messageid: <1288812744.25.0.755654545118.issue10284@psf.upfronthosting.co.za> |
| 2010年11月03日 19:32:21 | r.david.murray | link | issue10284 messages |
| 2010年11月03日 19:32:20 | r.david.murray | create |
|