-
This not really an issue, rather a question: For a special use case, in a production environment, I need to provide SMB1.0 Services to an IOT device running windows XP. How can I set the "min protocol" variable to support this? (Yes, I know about all the security issues, but this will be run on a small server on an isolated network segment) BR |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You can override the command in the compose file and add version: "3.5"
services:
samba:
image: crazymax/samba
container_name: samba
network_mode: host
command: smbd -F --debug-stdout --no-process-group --option='client min protocol=NT1' --option='server min protocol=NT1' --option='client ipc min protocol=NT1'
volumes:
- "./data:/data"
- "./public:/samba/public"
- "./share:/samba/share"
- "./foo:/samba/foo"
- "./foo-baz:/samba/foo-baz"
environment:
- "TZ=Europe/Paris"
- "SAMBA_LOG_LEVEL=0"
restart: always More info: |
Beta Was this translation helpful? Give feedback.
-
Maybe something has changes, adding the command makes two smbd run, one failing of course, resulting in the container stopping. I sadly still need NT1 for legacy crap. |
Beta Was this translation helpful? Give feedback.
You can override the command in the compose file and add
--option
to set min protocol toNT1
:More info: