search for: rsa4096

...ture: "gpg: key 0x0FC3042E345AD05D: 1 bad signature" which I highlighted below. Didn't seem to be a problem, but thought I'd point it out. I'd be glad to do additional tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub rsa4096/0x9F79B9CEB03232F9 2018-04-18 [C] [expires: 2019-04-18] Key fingerprint = 0B15 37E2 6423 4EF7 7934 7A79 9F79 B9CE B032 32F9 uid [ultimate] Winthrop Lyon Saville III <wink at saville.com > sub rsa4096/0xD232788D248BCF0E 2018-04-18 [S] [expires: 2019-04-18] sub rsa4...

I'm on an Arch Linux system: $ uname -a Linux wink-desktop 5.0.4-arch1-1-ARCH #1 SMP PREEMPT Sat Mar 23 21:00:33 UTC 2019 x86_64 GNU/Linux My gpg version is: $ gpg --version gpg (GnuPG) 2.2.15 libgcrypt 1.8.4 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later < https://gnu.org/licenses/gpl.html> This is free software: you are free to change and

...smbstatus output, "Locked files" section, there's a list of locked files (effectively opened files, since windows always locks a file which it opens) and corresponding pid of smbd process. How to map this information to user ID? Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...hich checks the msdfs entry in the file *listing* generated by samba. With my question above - "is no one using msdfs?" - I'm not sure it is worth the effort to actually fix this for 4.19. Maybe it is if the fix would be simple. Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...ND in the above debug log), and whole thing ends up in there. is_msdfs_link() is checked later. If I move is_msdfs_link() check right before openat_pathref_fsp_lcomp() call, it seems to work fine. Should such a move be done in the actual code? Thanks, /mjt-- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...o reduce the amount of files we ship further. I'm sorry for this become such large. It's been something I've been looking for quite some time. Samba has grown to a lot of various components, and I need help sorting these out.. :) Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

On 26/05/24 03:00, Michael Tokarev via samba wrote: > There's also /usr/sbin/samba_kcc in there, - should go either to samba-ad-client > or samba-ad-dc, I can't understand which one. samba-ad-dc. It is called by the server. >> BTW, do we really need samba_downgrade_db these days?? Changing format to the >> one used by samba 4.7, srsly?? I'd just remove this one :)

...his page mentions maximum samba version 4.4 and has been modified in 2017 (besides some formatting changes). What's the current situation? Also, what are the possible problems when trying to raise domain functional level using samba-tool? Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...idn't actually change (but the code is different), -- looks like the change happened in smbd_dirptr_get_entry itself. msdfs is broken in 4.19. It worked fine in 4.18. Is no one using msdfs? I wonder why I was the first to discover this? Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...ine and so far no user has alerted me ... > > winbind is installed, but somehow not started by "samba-ad-dc". Please check version of samba-ad-dc package, - is it the same as other samba package versions? Did samba-ad-dc start at all? /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

Am 07.06.24 um 08:45 schrieb Michael Tokarev: > Please check version of samba-ad-dc package, - is it the same as other > samba package versions? that package isn't installed according to "apt-cache policy" ! Seems it got lost while upgrading. > Did samba-ad-dc start at all? seemed like, but was very fast (so did nothing, as it seems) Did "apt install

...ng to follow. I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 broke case insensitive file access entirely. Only exact case filename works, no matter which value is set in "case sensitive" parameter. In 4.19, things works again. /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

On 07-06-2024 06:59, Michael Tokarev via samba wrote: > 07.06.2024 07:54, Jeremy Allison wrote: >>> msdfs is broken in 4.19.? It worked fine in 4.18. > > This is not entirely true. > >>> Is no one using msdfs?? I wonder why I was the first to discover this? >> >> There must not be a test for your specific use-case. >> >> MSDFS is tested in the

On 6/7/24 9:34 AM, Michael Tokarev via samba wrote: > I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20 > broke case insensitive file access entirely.? Only exact case > filename works, no matter which value is set in "case sensitive" > parameter. hm, can't reproduce: $ bin/smbclient -U "slow%x" //localhost/test smb: \> ls foo foo N

...nd locking etc doesn't work. Both shares are read-only, so we're not worrying about any symlink-based or other attacks. Without any smartness from samba it Just Work. But samba applies too much smartness here and breaks things badly. Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...n't change despite multiple users asked me to provide binaries for arm64 too, in addition to amd64. For this to work, build python (the one which is used to run wafsamba) should be de-coupled from host python (the one which we build for). Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

...fig: I am not using symlinks in the filesystem but 'msdfs proxy' in smb.conf.? Not sure if that can be > related to your finding? msdfs proxy is not affected in this context. It is the access to msdfs-symlink *files* which broke. Thanks, /mjt -- GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24. New key: rsa4096/61AD3D98ECDF2C8E 9D8B E14E 3F2A 9DD7 9199 28F1 61AD 3D98 ECDF 2C8E Old key: rsa2048/457CE0A0804465C5 6EE1 95D1 886E 8FFB 810D 4324 457C E0A0 8044 65C5 Transition statement: http://www.corpit.ru/mjt/gpg-transition-2024.txt

On Fri, Jun 07, 2024 at 11:54:28AM +0300, Michael Tokarev via samba wrote: >07.06.2024 10:13, Kees van Vloten via samba wrote: > >>There is a little difference with your config: I am not using >>symlinks in the filesystem but 'msdfs proxy' in smb.conf.? Not sure >>if that can be related to your finding? > >msdfs proxy is not affected in this context. It is

On Thu, 2 May 2024 13:44:47 +0300 Michael Tokarev via samba <samba at lists.samba.org> wrote: > Hi! > > In packaging/systemd/winbind.service, there's this ordering: > > After=network.target nmb.service > > Does winbind really need nmbd running? Well, no and yes ;-) No, if you are running Samba as an AD Unix domain member without SMBv1 (in which case, you do not

On Fri, Jun 07, 2024 at 07:16:06AM +0300, Michael Tokarev via samba wrote: >06.06.2024 19:33, Michael Tokarev via samba wrote: > >>For quite some time I'm trying to find what's going on with MSDFS referrals. >>Samba version is 4.19.6. >.. >>However, when opening the directory in question from client, this name is not >>shown in the listing.? Samba skips