Date: Wed, 15 Jul 2015 20:55:38 -0400 From: David Horn <dhorn2000@gmail.com> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: Re: mount_smbfs: syserr: Authetication error (option -N) Message-ID: <CAG7WopmY3Uh2POgujXNR2nMuK%2Bkby0kvHaG8-20-YnPPG=7kQw@mail.gmail.com> In-Reply-To: <20150714155848.7ee77773@freyja.zeit4.iv.bundesimmobilien.de> References: <20150714155848.7ee77773@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jul 14, 2015 at 9:58 AM, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > Running CURRENT and trying to mount a "share" provided by a M$ Windows 2012R2 > server via autofs fails with an authetication error. > > I tested successfully to mount the share via mount_smbfs manually, but whenever > I provide the option "-N" I receive this sticky authentication error. > > The manpage for mount_smbfs refers to /etc/nsmb.conf and therein the password > should be provided in cleartext or simple encrypted. Further, the FreeBSD > onboard tool "smbutil crypt SOMEPASSWORD" is suggested, creating a weak > obscured password hash for exactly the purpose I described above. > <snip> If your password is longer than 18 characters, then the smbutil crypt function will fail. I put in a bug report on this a few years ago. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=132302 Short answer, if you are running into this problem, either patch your smbutil function, or use a shorter password. There is a workaround patch included in the bug report. If you are having a different problem, good luck, but submit a report if it is not the same issue. Dave Horn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG7WopmY3Uh2POgujXNR2nMuK%2Bkby0kvHaG8-20-YnPPG=7kQw>