From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] samba: allow to configure server protocol version
Date: Mon, 02 Nov 2020 10:31:44 +0000 [thread overview]
Message-ID: <F08C4DC5-C258-437F-BCD7-EA2E2EEB4D0A@ipfire.org> (raw)
In-Reply-To: <20201101163856.4742-1-arne_f@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
Hello Arne,
This patch does not make sense to me because of two reasons:
1) There is no UI to configure this
2) Why would a user want to change this? You stated they are dangerous. Why would a user be qualified to change this? If the goal is to enable SMBv1, then I would suggest to rather have a checkbox with a big big warning sign that someone is doing something really really stupid.
If you just want to have a place to add some custom configuration options, why don’t we add a smb.conf.local file?
Best,
-Michael
> On 1 Nov 2020, at 16:38, Arne Fitzenreiter <arne_f(a)ipfire.org> wrote:
>
> add entries for server min/max protocol in /var/ipfire/samba/settings.
> This settings may be dangerous but sometimes they are needed so it will
> not showed in the cgi.
>
> Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
> ---
> html/cgi-bin/samba.cgi | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/html/cgi-bin/samba.cgi b/html/cgi-bin/samba.cgi
> index ec41adc5d..4b57c1add 100644
> --- a/html/cgi-bin/samba.cgi
> +++ b/html/cgi-bin/samba.cgi
> @@ -835,7 +835,16 @@ if ($sambasettings{'ENCRYPTION'} =~ m/(desired|required)/) {
> print FILE "smb encrypt = $1\n";
> }
>
> +if ($sambasettings{'SERVER_MIN_PROTOCOL'} ne "" ) {
> + print FILE "server min protocol = $sambasettings{'SERVER_MIN_PROTOCOL'}\n";
> +}
> +
> +if ($sambasettings{'SERVER_MAX_PROTOCOL'} ne "" ) {
> + print FILE "server max protocol = $sambasettings{'SERVER_MAX_PROTOCOL'}\n";
> +}
> +
> print FILE <<END;
> +
> # Export all printers
> [printers]
> path = /var/spool/samba/
> --
> 2.17.1
>
prev parent reply other threads:[~2020-11-02 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-01 16:38 Arne Fitzenreiter
2020-11-02 10:31 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F08C4DC5-C258-437F-BCD7-EA2E2EEB4D0A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox