VirtualBox

Ticket #13435 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

iScsi CHAP auth failing since v4.3.14 => fixed in next maintenance release

Reported by: MickSx Owned by:
Priority: major 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 Download (3.3 KB) - added by MickSx 3 years ago.
WireShark trace using v4.3.12
CHAP_v4.3.16.pcapng Download (2.4 KB) - added by MickSx 3 years ago.
WireShark trace using v4.3.16
X.TXT Download (29 bytes) - added by MickSx 3 years ago.
expected data for MD5
VBoxSvc.log Download (1.2 KB) - added by MickSx 3 years ago.
Extract from VBoxSvc.log

Change History

Changed 3 years ago by MickSx

WireShark trace using v4.3.12

Changed 3 years ago by MickSx

WireShark trace using v4.3.16

Changed 3 years ago by MickSx

expected data for MD5

Changed 3 years ago by MickSx

Extract from VBoxSvc.log

comment:1 Changed 3 years ago by MickSx

May be related to ticket #13386

comment:2 Changed 3 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 3 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.

comment:4 Changed 3 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of VBox 4.3.18.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use