similar to: mount.cifs return code = -128

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Time for another cifs-utils release! Nothing terribly earth shattering here. Some distros (like Fedora) are moving krb5 credcaches out of /tmp by default. Users of these distros will definitely want to upgrade. Highlights: * Fixes for mounting with '/' in usernames with sec=krb5 * Support for DIR: type krb5 ccaches * support for

Items in dmesg when FAT share's are accessed from web browser: CIFS VFS: bogus file nlink value 0 When accessed from FC/L (OFM (orthodox filemanager)): CIFS VFS: illegal date, month 0 day: 0 When the share is initially mounted: CIFS: Attempting to mount //hostname/E Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers CIFS VFS: Send error

Jeremy Allison via samba composed on 2020-04-23 09:24 (UTC-0700): > On Thu, Apr 23, 2020 at 02:59:18AM -0400, Felix Miata via samba wrote: >> Items in dmesg when FAT share's are accessed from web browser: >> CIFS VFS: bogus file nlink value 0 > nlink should never be zero. If an SMB server > returns that, then the CIFSFS client will have > to fake it to 1 at least.

Awhile ago I've set up a backup of my C6 home server to a D-Link NAS and it seems to be working. But when I mount a share with the backups I can't see files or directories not readable by others. I'm not very knowledgeable in cifs and probably missing some obvious options. noserverino option suggested on ubuntu forums didn't help. TIA

openSUSE v13.1 linux 3.11.10-11-desktop x86_64 samba 4.1.6 I recently upgraded an openSUSE server from v12.3 to v13.1. In the older version there was no problem about mounting a remote volume offered by an ancient OS/2 system. Now there is. Trying to mount it by command line: root:/home/sma-user3x> mount /t2 Retrying with upper case share name mount error(6): No such device or address

I have a debian machine called "debian" and a windows XP machine called "server". I have a permanent mounted read-only share called \\server\doc. My /etc/fstab looks like this: //server/doc /opt/chroot/mnt/server cifs credentials=/root/.smbmount,username=medical,uid=medical,file_mode=0755,dir_mode=0755,noserverino 0 0 This works well most of the time but at times I get a

Hi List, I have an appliance ("the client") which mounts a CIFS share from a Samba server - the Samba server usually runs on an Ubuntu system. Within the client, the root user executes a mount command like this: mount.cifs \\UBUNTUSERVER\archive /tmp/Default \ -o noserverino,user='someuser',pass='somepassword',uid='50',gid='7' That uid/gid pair

It is probably not strictly related to SAMBA itself but let me try to ask you for advice. Using smbmount I have mounted one of smb/cifs share to /root/test. This share has RW access and no authentication is required. Now, under DOSBox, whenever I try to mount /root/test I get this error (command sent under DOSBox: mount c /root/test). Directory /root/test doesn't exist. Any other directories,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It's been a while since our last release and Shirish's new cifs.idmap utility has now been merged. The last release was 4.9, so I've been a bit torn -- should I call this one 4.10 or 5.0? Then I figured...when in doubt, copy Linus. Since he just bumped the major version number of the kernel, this is now version 5.0. The main changes: -

So finally here is the solution that works for me. If you have any questions, just ask. I use pam_mount with the following volume definition in the "/etc/security/pam_mount.conf.xml": <volume fstype="cifs" server="server" path="home/%(USER)" mountpoint="/home/%(USER)" sgrp="domain users"

On 04/11/15 18:30, Ole Traupe wrote: > So finally here is the solution that works for me. If you have any > questions, just ask. > > I use pam_mount with the following volume definition in the > "/etc/security/pam_mount.conf.xml": > <volume fstype="cifs" server="server" path="home/%(USER)" > mountpoint="/home/%(USER)"

Hi, I have started using symbolic links on an SMB share and find that symbolic links whose target no longer exists cannot be removed on the client side. Example, on the SMB client side in an SMB-mounted directory: 1. Create a file and a relative symlink to it: $ touch a $ ln -s a b $ ls -l total 0 -rw-rw-r--. 1 andi andi 0 Jan 6 14:42 a lrwxrwxrwx. 1 andi andi 1

> > If by "key" you meant keytab then you were right. A keytab is a file > dedicated to contains credentials (https://kb.iu.edu/d/aumh or > http://web.mit.edu/Kerberos/krb5-1.12/doc/basic/keytab_def.html). > > Keytab are used when you want to automate actions which need > authentication. When some automated action requires credentials you > have to provide

Am 04.11.2015 um 14:49 schrieb mathias dufresne: > 2015-11-04 13:58 GMT+01:00 Ole Traupe <ole.traupe at tu-berlin.de>: > >> Mathias, thanks again! This sounds like a very reasonable approach. I know >> that with remote ssh and public key authentication you can set the limit to >> a single possible command. is this also possible with AD users? >> > I'm

> That is what I did. But it fails even when mounting manually: > 1. Connect on the desktop using domain user "yvan.masson" (either > graphically / TTY / SSH). Kerberos ticket is properly created. > 2. Running "sudo mount -t cifs //ad.FOO.BAR.LOCAL/Echange /mnt -o > user=yvan.masson,cruid=yvan.masson,sec=krb5" fails with "Required key > not

Hi all, this is not really a Samba question, but related, and I hope that some of you are using this and can tell me what I am doing wrong. On a member server, I can mount my shares by hand specifying "-o username=xxx,domain=yyy,password=zzz". But as soon as I put "sec=krb5" in the mount options (and leaving out the password part), I get this error: # mount error(126):

On Mon, 29 Jan 2024 16:42:20 -0800 Peter Carlson via samba <samba at lists.samba.org> wrote: > > On 1/29/24 13:08, Rowland Penny via samba wrote: > > On Mon, 29 Jan 2024 12:51:37 -0800 > > Peter Carlson via samba<samba at lists.samba.org> wrote: > > > > > >> Just did a quick test, the big T comes after setting permissions in > >>

Mathias, thanks again! This sounds like a very reasonable approach. I know that with remote ssh and public key authentication you can set the limit to a single possible command. is this also possible with AD users? Unfortunately, I don't have 'multiuser' support in my current cifs-utils version 4.8. So I would end up with your designated user being the owner of all the files and

Le 10/03/2020 ? 11:21, Rowland penny via samba a ?crit?: > On 10/03/2020 10:10, Yvan Masson via samba wrote: >> Le 10/03/2020 ? 10:37, Rowland penny via samba a ?crit?: >>> On 10/03/2020 09:18, Yvan Masson via samba wrote: >>>> If think I did not properly explain my setup, sorry for that: Samba >>>> here is not sharing anything. It is just used for

First please note the following is not really linked to your NFS question, it's more related to automation, credentials everywhere and how to secure them a little bit. The point dealing with keytab or credentials in general when used for automation, as these credentials can potentially used by some attacker, is to create dedicated user which can perform only what it is supposed to perform.