80
edits
Difference between revisions of "BoshIssues"
Jump to navigation
Jump to search
no edit summary
(→Status: textual improvement) |
|||
| Line 221: | Line 221: | ||
M-Link's next release will do this for TLS-based auth (ie, X.509 strong auth over BOSH) - I'm not so sure what we should do for Basic, if anything. | M-Link's next release will do this for TLS-based auth (ie, X.509 strong auth over BOSH) - I'm not so sure what we should do for Basic, if anything. | ||
===Status=== | |||
More discussion is needed. | |||
==Key encoding== | |||
===Issue=== | |||
Section 15.3 is unclear about the encoding of the key, specifically, whether the hexadecimal representation uses lowercase or uppercase versions of the alphabetic characters. The SHA-1 specification (RFC 3174) seems to imply that the characters are uppercase, however many libraries produce lowercase. We need to clarify this. | |||
===Status=== | ===Status=== | ||
More discussion is needed. | More discussion is needed. | ||