diff options
| author | David Disseldorp <[email protected]> | 2019-09-12 11:55:45 +0200 |
|---|---|---|
| committer | Martin K. Petersen <[email protected]> | 2019-10-22 22:14:24 -0400 |
| commit | 9cef2a7955f2754257a7cddedec16edae7b587d0 (patch) | |
| tree | 19c477a6e51f9e7cf3bf55ee338b2231c203ab05 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | c695793b52216ad6a11ce952fc8d29f3a9d0c7cd (diff) | |
scsi: target: compare full CHAP_A Algorithm strings
RFC 2307 states:
For CHAP [RFC1994], in the first step, the initiator MUST send:
CHAP_A=<A1,A2...>
Where A1,A2... are proposed algorithms, in order of preference.
...
For the Algorithm, as stated in [RFC1994], one value is required to
be implemented:
5 (CHAP with MD5)
LIO currently checks for this value by only comparing a single byte in
the tokenized Algorithm string, which means that any value starting with
a '5' (e.g. "55") is interpreted as "CHAP with MD5". Fix this by
comparing the entire tokenized string.
Reviewed-by: Lee Duncan <[email protected]>
Reviewed-by: Mike Christie <[email protected]>
Signed-off-by: David Disseldorp <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions