search for: rsa2048

Looks like the GPG key we use to sign our RPMs is not longer good with EL9: # rpm --import RPM-GPG-KEY-nwra error: RPM-GPG-KEY-nwra: key 1 import failed gpg key info: sec rsa2048/35DDB0B86218AC2F created: 2017-08-16 expires: never usage: SC trust: ultimate validity: ultimate ssb rsa2048/6A7FBC1E9DB22E8E created: 2017-08-16 expires: never usage: E Can someone explain what I need to do to make things compatible with EL9? Thank you! -- Or...

...wrote: > On 01/06/2022 19:51, Orion Poplawski wrote: >> Looks like the GPG key we use to sign our RPMs is not longer good with EL9: >> >> # rpm --import RPM-GPG-KEY-nwra >> error: RPM-GPG-KEY-nwra: key 1 import failed >> >> gpg key info: >> >> sec? rsa2048/35DDB0B86218AC2F >> ????? created: 2017-08-16? expires: never?????? usage: SC >> ????? trust: ultimate????? validity: ultimate >> ssb? rsa2048/6A7FBC1E9DB22E8E >> ????? created: 2017-08-16? expires: never?????? usage: E >> >> Can someone explain what I need to do...

In the 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

...[ultimate] Winthrop Lyon Saville III <wink at saville.com > sub rsa4096/0xD232788D248BCF0E 2018-04-18 [S] [expires: 2019-04-18] sub rsa4096/0x9220D48FF6008D0D 2018-04-18 [E] [expires: 2019-04-18] sub rsa4096/0x92BB19D0D4F68457 2018-04-18 [A] [expires: 2019-04-18] pub rsa2048/0x7F2D434B9741E8AC 2011-04-10 [SC] Key fingerprint = 4AA4 767B BC9C 4B1D 18AE 28B7 7F2D 434B 9741 E8AC uid [ unknown] Pierre Schmitz <pierre at archlinux.de> sub rsa2048/0xE9B9D36A54211796 2011-04-10 [E] wink at wink-desktop:~ $ gpg --import Documents/keys-crypto/h...

...s no test which 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

...ist-packages/samba/netcmd/domain/leave.py", line 59, in run s3_net.leave(keep_account) (all tools also display this out-of-context warning about using passwords on command line, which I don't do). How to remove this machine from a domain? 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

...AME_NOT_FOUND 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

On Mon, 13 Aug 2018, Blumenthal, Uri - 0553 - MITLL wrote: > Lack of time on the Open Source projects is understandable, and not uncommon. > > However, PKCS11 has been in the codebase practically forever - the ECC > patches that I saw did not alter the API or such. It is especially > non-invasive when digital signature is concerned. > > Considering how long those patches have

...39;d love to 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 :)

...pported. This 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

...t_entry() didn'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

...ings work fine 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

...ore debugging 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

...ame file, and 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

...is part didn'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

...th 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 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