Opened 3 years ago

Last modified 2 years ago

#316 new defect

Kerberos5 support encryption support and NTLMvl1 support checkbox defaults and behavior incorrect

Reported by: Gregg Young Owned by:
Priority: major Milestone: GUI Tools 1.0.0
Component: Samba Client GUI Version: Server 3.6.x
Keywords: Cc:

Description

These are checked by default and should not be. While NTLMv1 does not support kerberos or encryption you can select all 3 together. NTLMv1 should uncheck the other 2 when selected and should be unchecked when one of the others is selected.

Attachments (1)

evfsgui.diff (2.8 KB) - added by Gregg Young 3 years ago.

Download all attachments as: .zip

Change History (6)

comment:1 Changed 3 years ago by Gregg Young

I found an issue with the variable naming which may be the cause of this. These weren't being added to the ini file either. I don't have VX-Rexx so I couldn't try my fix. I have attached it if anyone would like to try it.

Changed 3 years ago by Gregg Young

Attachment: evfsgui.diff added

comment:2 Changed 2 years ago by Lewis Rosenthal

This is actually working now (ArcaMapper 2.6 / EVFSGUI trunk), but the checkboxes start out as all checked. Once unchecking all and then checking, say NTLMv1 (on either the popup on the Network neighborhood tab or on the New Resource Advanced tab), the other conflicting options are greyed out.

Unfortunately, however, functionally, these checkboxes do not appear to pass the proper options to NetDrive (according to the debug window output), which should be:

KRB5SUPPORT=0/1
NTLMv1SUPPORT=0/1
ENCRYPTIONSUPPORT=0/1

All three should be passed, and they must not conflict. NTLMv1SUPPORT=1 is required when connecting to an NTLMv1-only host (otherwise, an error 58 will result). Samba 4 will not automatically fall back to NTLMv1 unless explicitly told to do so. When this parameter is missing, the farthest we default to NTLMv2, which is unintelligible to an NTLMv1-only host.

comment:3 Changed 2 years ago by Lewis Rosenthal

Priority: minormajor

comment:4 Changed 2 years ago by Lewis Rosenthal

Oddly, I was just able to get these options passed when mapping from the Network neighborhood tab. I had to uncheck all and then check NTLMv1. That same procedure does not seem to get them passed if I map from the New Resource tab.

Last edited 2 years ago by Lewis Rosenthal (previous) (diff)

comment:5 Changed 2 years ago by Herwig Bauernfeind

They were indeed not setup properly during start.

Note: See TracTickets for help on using tickets.