From: "Lott, Christopher M" <clott-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Ubuntu SecurityFlags at boot
Date: Mon, 01 Oct 2012 18:23:39 -0400 [thread overview]
Message-ID: <506A17EB.2050908@appcomsci.com> (raw)
I hope it's not too late to reply to this thread from August 2012, and
that someone can please find time to explain to me how to set security
flags for CIFS.
In a nutshell I'm trying to connect a freshly installed ubuntu 12.04
desktop as a client to get files from an old samba server that demands
passwords as plaintext. No printing, nothing fancy, just file service.
Is there still a feature in Ubuntu 12.04 to allow this, possibly by
manipulating these security flags?
I'm basically doing just this:
sudo mount -t cifs //myoldtiredserver/lott /mnt
And watching /var/log/kern.log I see this:
Oct 1 18:14:57 cltp kernel: [ 3397.554888] CIFS VFS: Server requests
plain text password but client support disabled
Oct 1 18:14:57 cltp kernel: [ 3397.616357] CIFS VFS: cifs_mount failed
w/return code = -13
All attempts to echo a value to a magic file in /proc/fs/cifs such as
the one shown below are met with permission denied, even with sudo:
$ sudo echo 0x30030 > /proc/fs/cifs/SecurityFlags
bash: /proc/fs/cifs/SecurityFlags: Permission denied
Please let me know if I'm not asking sensible questions. :/ Thanks in
advance for any help!
> It would be possible to build cifs.ko to enable plain text passwords
> permanently, but may be simpler to just set this in one of the init
> scripts. Generally we want to discourage anyone from using
> authentication types other than ntlmv2 and kerberos for obvious
> security reasons.
>
> On Sun, Aug 5, 2012 at 6:31 AM, <blueduck@...> wrote:
> > Hi,
> >
> > Looking at fs/cifs/README, I managed to mount shares with plaintext
> passwords (using Kubuntu 12.04)
> with "echo 0x30030 > /proc/fs/cifs/SecurityFlags". But it as to be
done after each boot.
> >
> > Is there any configuration file to modify to make the change permanent?
next reply other threads:[~2012-10-01 22:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 22:23 Lott, Christopher M [this message]
[not found] ` <506A17EB.2050908-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
2012-10-02 1:48 ` Ubuntu SecurityFlags at boot Jeff Layton
[not found] ` <20121001214848.45781bb3-4QP7MXygkU+dMjc06nkz3ljfA9RmPOcC@public.gmane.org>
2012-10-02 5:24 ` Lott, Christopher M
[not found] ` <506A7AA9.2090606-as7a0GIpyE2tG0bUXCXiUA@public.gmane.org>
2012-10-02 11:19 ` Jeff Layton
[not found] <S1753625Ab2HELY7/20120805112459Z+242@vger.kernel.org>
[not found] ` <S1753625Ab2HELY7/20120805112459Z+242-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
2012-08-05 11:31 ` blueduck-GANU6spQydw
[not found] ` <484724139.8236317.1344166282900.JavaMail.root-TwAYtqM7ZI5mpWzFTGZ+Dhh1pbbyJDp15NbjCUgZEJk@public.gmane.org>
2012-08-05 15:29 ` Steve French
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=506A17EB.2050908@appcomsci.com \
--to=clott-as7a0gipye2tg0buxcxiua@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.