Skip to content

Fix Samba configuration for Samba 4.20.6 compatibility#15064

Closed
soaresden wants to merge 2 commits intobatocera-linux:masterfrom
soaresden:fixSMB
Closed

Fix Samba configuration for Samba 4.20.6 compatibility#15064
soaresden wants to merge 2 commits intobatocera-linux:masterfrom
soaresden:fixSMB

Conversation

@soaresden
Copy link
Copy Markdown

Description

This PR fixes Samba network sharing on Batocera by updating the configuration to work with modern Samba versions (4.20.6).

Issues Fixed

  • Samba mode was inactive despite service running
  • Connection failures due to deprecated SMB1 protocol negotiation
  • Configuration warnings from empty [nobody] share definition

Changes

  • Remove deprecated SMB1 protocol: Replaced client min protocol = NT1 with min protocol = SMB2 and max protocol = SMB3
  • Remove empty share definition: Deleted the empty [nobody] section at end of smb.conf which caused warnings
  • Updated configuration comments to clarify SMB protocol settings

Testing

  • Samba service starts without warnings
  • Network shares are accessible via \\BATOCERA\share
  • Guest access works as expected
  • Tested with Samba 4.20.6

Files Changed

  • board/batocera/fsoverlay/etc/samba/smb.conf

Checklist

  • Configuration tested and working
  • No breaking changes for existing users
  • Maintains backward compatibility with share access

## Description
This PR fixes Samba network sharing on Batocera by updating the configuration
to work with modern Samba versions (4.20.6).

## Issues Fixed
- Samba mode was inactive despite service running
- Connection failures due to deprecated SMB1 protocol negotiation
- Configuration warnings from empty [nobody] share definition

## Changes
- **Remove deprecated SMB1 protocol**: Replaced `client min protocol = NT1`
  with `min protocol = SMB2` and `max protocol = SMB3`
- **Remove empty share definition**: Deleted the empty `[nobody]` section
  at end of smb.conf which caused warnings
- Updated configuration comments to clarify SMB protocol settings

## Testing
- Samba service starts without warnings
- Network shares are accessible via `\\BATOCERA\share`
- Guest access works as expected
- Tested with Samba 4.20.6

## Files Changed
- `board/batocera/fsoverlay/etc/samba/smb.conf`

## Checklist
- [x] Configuration tested and working
- [x] No breaking changes for existing users
- [x] Maintains backward compatibility with share access
@crcerror
Copy link
Copy Markdown
Contributor

crcerror commented Jan 4, 2026

No breaking changes for existing users

I have my doubts

If you do such changes then please add them also to changelog. Several NAS systems just use SMB1 (yes unsecure.....) but give users a chance to reconfigure the systems by announcing this.

Fix Samba configuration for Samba 4.20.6 compatibility

- Add comments and fallback option for users with legacy SMB1-only systems
- Update changelog with breaking change note

This change improves security and compatibility with newer Samba versions while
allowing users with old NAS systems to revert to SMB1 if needed.
@crcerror
Copy link
Copy Markdown
Contributor

crcerror commented Jan 4, 2026

Just read your hint. I see issues here...

  1. the file you are speaking about is a system file so changes are not kept permanent
  2. if you uncomment the key it is still overwritten to value SMB2

@dmanlfc
Copy link
Copy Markdown
Collaborator

dmanlfc commented Jan 6, 2026

samba 4.23.4 works fine here... it's unclear what you're trying to fix.
the nt1 compatibility has been there for 5 years. why would we restrict it?

@soaresden
Copy link
Copy Markdown
Author

soaresden commented Jan 6, 2026 via email

@dmanlfc
Copy link
Copy Markdown
Collaborator

dmanlfc commented Jan 6, 2026

we are not worried about security... obviously... it was set to provide the widest range of compatibility at the time. as crcerror pointed out legacy systems will need it.

@soaresden soaresden closed this Feb 13, 2026
@soaresden soaresden deleted the fixSMB branch February 13, 2026 09:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants