Project

General

Profile

Actions

Bug #705

closed

smb config needs updating

Added by Hammel over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Immediate
Assignee:
Category:
00 - Basic Build Issues
Target version:
Start date:
18 Mar 2019
Due date:
% Done:

100%

Estimated time:
Severity:
04 - Low

Description

The latest boot is showing the following in dmesg:

[ 51.971329] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[ 52.913554] CIFS VFS: Unable to select appropriate authentication method!
[ 52.913587] CIFS VFS: Send error in SessSetup = -22

It's a config update that hasn't been propagated to PiBox's smb configuration.

Actions #1

Updated by Hammel over 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10

This appears to be a change to the smb command in piboxd, where the "-o <options>" needs to include "vers=1" or "vers=3" or something. It's not clear what it should be but "vers=1" seems to be the fallback for the old default setting (which is no longer set).

Also, or possibly in place of, I can try removing ",sec=ntlm" which is set in piboxd:smb.c in the default command.

Actions #2

Updated by Hammel over 2 years ago

  • % Done changed from 10 to 50

"vers=1.0" fixes this problem. At the same time, I'm implementing the option of disabling both SMB and stream handling in piboxd. This will allow piboxd to be more lightweight on systems like Xeon.

Currently need to implement -x option for piboxd's cross.sh, as was done for the launcher, so the build picks up the proper app.cfg file.

Actions #3

Updated by Hammel over 2 years ago

  • Priority changed from Immediate to Urgent
  • % Done changed from 50 to 80

Fixes tested, committed and pushed - including metabuild.

Changes seem to work but it's unclear if this fixes the reported issue.

Moving this down the priority list and will recheck again later to see if the problem shows up anymore.

Actions #4

Updated by Hammel over 2 years ago

  • Severity changed from 05 - Very Low to 04 - Low
Actions #5

Updated by Hammel almost 2 years ago

  • Priority changed from Urgent to Immediate
Actions #6

Updated by Hammel over 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 80 to 100

Verified that this problem has been addressed. However, there were additional logs being dumped to syslog on a frequent basis. These have to do with smb thinking it needs to look in /media/usb but that doesn't exist until we stuff a USB stick in the port.

Those messages were filling up /var/log/messages and there is nothing to rotate that yet. So I disabled logging via syslog with

syslog = 0

in smb.conf in the dev platform build. This moved the messages to /var/log/samba/smbd.log, which is rotated at 50k.

Tested, committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF