Ticket #13435 (closed defect: fixed)
iScsi CHAP auth failing since v4.3.14 => fixed in next maintenance release
| Reported by: | MickSx | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 4.3.16 |
| Keywords: | iscsi CHAP | Cc: | |
| Guest type: | Windows | Host type: | Windows |
Description
I am seeing a problem with iScsi authentication since version 4.3.14 same problem on v4.3.16
I am attaching two Wireshark traces - one from each version of Vbox. I have forced the target to use the same challenge in both cases.
The response returned by 4.3.12 is the same as I would expect if calculating manually. MD5 of attached file x.txt gives MD5(x.txt)= 3d3de31c2fdba8db30f40d10a80650d3
Attachments
-
CHAP_v4.3.12.pcapng
(3.3 KB) -
added by MickSx 9 years ago.
- WireShark trace using v4.3.12
-
CHAP_v4.3.16.pcapng
(2.4 KB) -
added by MickSx 9 years ago.
- WireShark trace using v4.3.16
-
X.TXT
(29 bytes) -
added by MickSx 9 years ago.
- expected data for MD5
-
VBoxSvc.log
(1.2 KB) -
added by MickSx 9 years ago.
- Extract from VBoxSvc.log
Change History
Changed 9 years ago by MickSx
-
attachment
CHAP_v4.3.12.pcapng
added
comment:2 Changed 9 years ago by frank
Ticket #13386 talks about 4.3.12 being the first release where it does not work while you say that 4.3.12 worked. Is that still true?
I see that you are on a Windows host. Could you provide a VBoxStartup.log file of such a VM session where you try to connect to an iSCSI target? There is a slight chance that the problem results from some hardening changes we did in VBox 4.3.14. VBoxStartup.log would probably show that.
comment:3 Changed 9 years ago by aeichner
- Summary changed from iScsi CHAP auth failing since v4.3.14 to iScsi CHAP auth failing since v4.3.14 => fixed in next maintenance release
Thanks for the report, this is indeed a regression introduced with 4.3.14. This will be fixed in the next maintenance release.
WireShark trace using v4.3.12