similar to: [Announce] Samba 4.21.2 Available for Download

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.5 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15590: libldb: performance issue with indexes (ldb 2.9.2 is already ???? released). o? Ralph Boehme <slow at samba.org> ?? * BUG 15624: DH reconnect error

Release Announcements --------------------- This is the latest stable release of the Samba 4.20 release series. Changes since 4.20.5 -------------------- o? Douglas Bagnall <douglas.bagnall at catalyst.net.nz> ?? * BUG 15590: libldb: performance issue with indexes (ldb 2.9.2 is already ???? released). o? Ralph Boehme <slow at samba.org> ?? * BUG 15624: DH reconnect error

On 2020-03-30 14:33, Rowland penny via samba wrote: > It might help if you don't crop lines like the above from your logs, out > of context they are meaningless. > > If you are going to post log fragments, post the entire log fragment and > a few lines above and below it. Sorry. Here a full excerpt: > [2020/03/30 14:56:31.559263, 0]

Dear all, we updated to 4.12.10-10 using the sernet packages. After approx. 30 minutes I obtainted the following messages in syslog: root at ctdb-ho-2:~# journalctl -f -- Logs begin at Wed 2020-11-11 08:53:27 CET. -- Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.616823, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory:

Hello. I'm seeing several of the above messages in my smbd logs. I see three different kinds: > close_directory: Could not delete share entry for . > close_directory: Could not delete share entry for {filename} > close_remove_share_mode: Could not delete share entry for file {filename} I could find no explanation on their meaning. Anyone has a pointer? bye & Thanks av.

Encountering a strange one... has been occuring since samba 4.15.x and continues to occur even in 4.17.5 and 4.18 Issue does not occur in earlier versions (4.13.x) and have switched back and forth between versions to confirm. Servers are winbind joined, PAM and krb5 auth, all seems to work fine (reading, writing, creating, moving) until trying to delete an empty folder on the share from Windows

On 2020-03-31 12:21, Rowland penny via samba wrote: > A 'share entry' is exactly that, a file or directory You mean, it's a client trying to delete a file/directory? From what I can see, crossing smbd's log and audit log, the message > [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry

On Wed, Mar 15, 2023 at 04:53:16PM +0000, Rowland Penny via samba wrote: > > >On 15/03/2023 16:47, Jeremy Allison via samba wrote: >>On Wed, Mar 15, 2023 at 11:29:10AM -0400, CaptainTrips28 via samba wrote: >>>Encountering a strange one... has been occuring since samba 4.15.x and >>>continues to occur even in 4.17.5 and 4.18 >>> >>>Issue does not

On Jan 17, 2017, at 9:57 AM, Douglas E Engert <deengert at gmail.com> wrote: > On 1/16/2017 2:09 PM, Ron Frederick wrote: >> I?m working on an implementation of ?gssapi-with-mic? authentication for my AsyncSSH package and trying to get it to interoperate with OpenSSH. I?ve gotten it working, but there seems to be a discrepancy between the OpenSSH implementation and RFC 4462.

I?m working on an implementation of ?gssapi-with-mic? authentication for my AsyncSSH package and trying to get it to interoperate with OpenSSH. I?ve gotten it working, but there seems to be a discrepancy between the OpenSSH implementation and RFC 4462. Specifically, RFC 4462 says the following in section 3.4: Since the user authentication process by its nature authenticates only the client,

Hello, Based on the GSS userauth code that went into 3.7p1, I have made a patch to make OpenSSH support an alternative Kerberos 5 implementation called Shishi, via an alternative GSS-API implementation called GSSLib. The reason behind this message is mostly to let you know that another pair of eyes has been reading GSS userauth code in OpenSSH, and my impression is that it looks pretty good. I

Hi guys I have a problem with Samba 4.0 shares covered by scannedonly VFS. Example configuration of one of those shares: path = /foo/bar/baz read only = No browseable = No vfs objects = scannedonly scannedonly:domain_socket = True scannedonly:socketname = /var/lib/scannedonly/scan scannedonly:hide_nonscanned_files = True scannedonly:allow_nonscanned_files = False Whenever I

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

This is just a information in case somebody runs into the same issue: I was unable to upload drivers to a samba-server (3.0.28a and 3.0.29) via the windows add printer wizard. The driver files started uploading, then processing stopped saying the driver is not compatible to windows xp. In the logs the following message popped up. However some files could be copied: [2008/05/27 10:30:09, 0]

samba 4.4..x version no problem. samba 4.5.rc1 4.5.rc2 4.5.-test all versions problem. winbind max clients = 2000 line. server crashes in 1 day.. :((( my smb file here. winbindd:use external pipes = true winbind cache time = 300 winbind reconnect delay = 30 winbind request timeout = 60 winbind max clients = 2000 # winbind max clients = 200 winbind max domain

(I hope this message is appropriate for these lists. If not, please tell me and I won't do it again.) Hi All. There will be a new release of OpenSSH in a couple of weeks. This release contains Kerberos and GSSAPI related changes that we would like to get some feedback about (and hopefully address any issues with) before the release. I encourage anyone with an interest in

Hi, all. I'm making my first foray into AEL. I'm starting with a simple macro, but I've already encountered an odd behaviour. I'm wondering if someone can shed some insight: Asterisk 1.2.9.1 macro newPlaceCallPSTN { s => { TIMEOUT(absolute)=7200; NoOp(Analog Out List: ${ANALOGOUT}); ChanIsAvail(${ANALOGOUT}); NoOp(Available Out List:

The Wine development release 3.9 is now available. What's new in this release (see below for details): - OpenGL core contexts enabled by default in Direct 3D. - Beginnings of Direct 3D 12 implementation using vkd3d. - More support for the Task Scheduler. - Some more Task Dialog support. - Better arrow support in GdiPlus. - Various bug fixes. The source is available from the

Hi! I?m new to the list, and I?m not really having a ?problem?, but I?m seeing something in my log files that I wonder if I should be concerned. I?ve been using Dovecot (dovecot-0.99.14-8.fc4) on my Fedora Core 4 (kernel 2.6.17-1.2142_FC4) machine from quite some time. For the last few days, I?ve been seeing this in my daily ?Logwatch? e-mail: dovecot: Authentication Failures: