Displaying 20 results from an estimated 900 matches similar to: "SAMBA_VERSION_VENDOR_SUFFIX in VERSION"
2019 Apr 04
2
Unable to verify of llvm sources with the .sig files
With the new signature file I was able to verify, but there was
still a bad signature: "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
2024 Jun 07
1
smbstatus: who opened the file?
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
2019 Mar 29
2
Unable to verify of llvm sources with the .sig files
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
2024 Jun 07
2
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
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 autobuild test suite. Can
> you articulate the problem well enough we can
> build a
2024 Jun 20
3
leaving a domain?
Hi!
I joined a newly installed samba (4.20.1) server to a domain, - just testing
things. Now I want to remove this test server from a domain, but I can't:
root at svdcm2:/# samba-tool domain leave -U tls\\mjt-adm
WARNING: Using passwords on command line is insecure. Installing the setproctitle python module will hide these from shortly after program start.
Password for [TLS\mjt-adm]:
2024 May 26
1
classifying samba componens and sorting into debian binary packages
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 :)
2024 Jun 07
1
DC upgraded to 4.20.1 - issues
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
2024 Jun 07
1
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
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
2024 Jun 07
1
4.20: case (in)sensitive is broken
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
2024 Jun 11
1
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
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
2024 Jun 20
1
leaving a domain?
On 6/20/24 2:03 PM, Michael Tokarev via samba wrote:
> How to remove this machine from a domain?
net ads leave ...
-slow
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL:
2024 Jun 20
1
leaving a domain?
On Thu, 20 Jun 2024 15:19:35 +0300
Michael Tokarev <mjt at tls.msk.ru> wrote:
> 20.06.2024 15:16, Rowland Penny via samba wrote:
> > On Thu, 20 Jun 2024 15:07:11 +0300
> > Michael Tokarev via samba <samba at lists.samba.org> wrote:
> >
> >> 20.06.2024 15:03, Michael Tokarev via samba wrote:
>
> >> Still, it'd be nice if samba-tool domain
2024 May 02
2
winbind: does it actually depend on nmbd? and network-online?
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
2024 Jun 07
1
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
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
2024 Jun 20
1
leaving a domain?
On Thu, 20 Jun 2024 15:07:11 +0300
Michael Tokarev via samba <samba at lists.samba.org> wrote:
> 20.06.2024 15:03, Michael Tokarev via samba ?????:
> > Hi!
> >
> > I joined a newly installed samba (4.20.1) server to a domain, -
> > just testing things.? Now I want to remove this test server from a
> > domain, but I can't:
> >
> >
> >
2024 Jun 07
2
4.20: case (in)sensitive is broken
On Fri, Jun 07, 2024 at 04:59:29PM +0300, Michael Tokarev via samba wrote:
>07.06.2024 16:57, Michael Tokarev wrote:
>>It boils down to having wide links = yes (and wide links = no).
>
>It boils down to having wide links = yes (and UNIX EXTENSIONS = no) :)
Wide links is problematic. I'd love to just remove it :-).
2024 Jun 06
1
missing msdfs referrals from samba directory listing: wrong order in smbd_dirptr_get_entry()?
Hi!
For quite some time I'm trying to find what's going on with MSDFS referrals.
Samba version is 4.19.6.
We've global host msdfs = yes (the default anyway), and for a share in question,
msdfs root = yes. testparam confirms the settings.
There's a symlink created in the root dir of the share, which points to the same
server but different path:
dfstest =>
2024 Jun 07
1
4.20: case (in)sensitive is broken
On Fri, Jun 07, 2024 at 08:21:26PM +0300, Michael Tokarev wrote:
>But samba applies too much smartness here and breaks things badly.
Fair enough. Can you post a minimal smb.conf and directory
setup that reproduces the problem and how to demo it with smbclient
command lines please ? I know I'm asking to be spoon-fed but my time for
Samba these days is quite limited and this would aid
2024 Jun 07
2
DC upgraded to 4.20.1 - issues
I run 2 DCs at a site, Debian 12.5, so far samba-4.19.6 from backports.
Today I upgraded one of them, this brought samba-4.20.1
Now on this one DC stuff like "wbinfo -g" fails:
# wbinfo -g
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
failed to call wbcListGroups: WBC_ERR_WINBIND_NOT_AVAILABLE
Error looking up domain
2024 Jun 27
1
bind9 failure when using dlz_bind
Using latest samba 4.20.2 from Debian Trixie repositories, the latest
bind9 upgrade to version 9.19.24 fails to start on DC's using dlz_bind.?
Reverting back to bind9 9.19.21 restores full functionality.? On
standalone systems running the same samba version with the latest bind9,
named starts with no issues.
The most recent dlz_bind version available is dlz_bind9_18.so. Since the
kernel