Displaying 20 results from an estimated 50000 matches similar to: "[Announce] Samba 4.21.0rc1 Available for Download"
2024 Aug 20
0
[Announce] Samba 4.21.0rc3 Available for Download
Release Announcements
=====================
This is the third release candidate of Samba 4.21.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.21 will be the next version of the Samba suite.
UPGRADING
=========
Hardening of "valid
2024 Aug 20
0
[Announce] Samba 4.21.0rc3 Available for Download
Release Announcements
=====================
This is the third release candidate of Samba 4.21.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.21 will be the next version of the Samba suite.
UPGRADING
=========
Hardening of "valid
2024 Aug 27
0
[Announce] Samba 4.21.0rc4 Available for Download
Release Announcements
=====================
This is the fourth release candidate of Samba 4.21.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.21 will be the next version of the Samba suite.
UPGRADING
=========
Hardening of "valid
2024 Aug 27
0
[Announce] Samba 4.21.0rc4 Available for Download
Release Announcements
=====================
This is the fourth release candidate of Samba 4.21.? This is *not*
intended for production environments and is designed for testing
purposes only.? Please report any defects via the Samba bug reporting
system at https://bugzilla.samba.org/.
Samba 4.21 will be the next version of the Samba suite.
UPGRADING
=========
Hardening of "valid
2024 Sep 02
0
[Announce] Samba 4.21.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.21 release series.
Please read the release notes carefully before upgrading.
Hardening of "valid users", "invalid users", "read list" and "write list"
=========================================================================
In previous versions of Samba, if a
2024 Sep 02
0
[Announce] Samba 4.21.0 Available for Download
Release Announcements
---------------------
This is the first stable release of the Samba 4.21 release series.
Please read the release notes carefully before upgrading.
Hardening of "valid users", "invalid users", "read list" and "write list"
=========================================================================
In previous versions of Samba, if a
2013 Jan 14
3
Samba4 AD delegation to read userPassword attribute
Hello Samba group,
I ran into a problem concerning Dovecot LDAP authentication to the Samba4 Active Directory.
Background: I want to install a Openchange+Samba4 environment using Sogo, Dovecot and Postfix. I didn't want to use openldap as described in the Openchange documentation, why should I use 2 LDAP databases?
Fedora 17, latest updates applied
Samba: Version 4.1.0pre1-GIT-813bd03
2015 Jun 15
0
Samba upgrade issue . . .
On 15/06/15 11:52, Steve Ankeny wrote:
> I have a "Samba | SOGo | OpenChange" server running in VMware.
>
> I get the following message when running 'apt-get upgrade' --
>
> The following packages have been kept back:
> libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind
> libpam-winbind libsmbclient libwbclient0 openchangeproxy
>
2011 Apr 23
1
ldapsearch with samba4
Hi,
I've got ldapsearch mostly working:
root at morannon:/usr/local/samba/private/tls# ldapsearch
'(sAMAccountName=dumaresq)'
SASL/GSSAPI authentication started
SASL username: administrator at XXX
SASL SSF: 56
SASL data security layer installed.
# extended LDIF
#
# LDAPv3
# base <> (default) with scope subtree
# filter: (sAMAccountName=dumaresq)
# requesting: ALL
#
results in
2015 Jun 15
0
Samba upgrade issue . . .
and just a comment..
when i look at :
http://inverse.ca/ubuntu-nightly/dists/trusty/trusty/binary-amd64/Packages
/search for : 2:4.1.18+dfsg-3~inverse1
Replaces: libpam-winbind (<< 2:3.6.5-2), samba (<= 2.2.3-2), winbind (<< 2:3.5.11~dfsg-3), winbind4
=> winbind4..
this all is build agains the old "samba4" naming which is not used anymore.
anyway..
i see..
2015 Jun 15
1
Samba upgrade issue . . .
On 15/06/15 14:01, L.P.H. van Belle wrote:
> and just a comment..
>
> when i look at :
> http://inverse.ca/ubuntu-nightly/dists/trusty/trusty/binary-amd64/Packages
> /search for : 2:4.1.18+dfsg-3~inverse1
> Replaces: libpam-winbind (<< 2:3.6.5-2), samba (<= 2.2.3-2), winbind (<< 2:3.5.11~dfsg-3), winbind4
> => winbind4..
>
> this all is build agains the
2015 Jun 15
3
Samba upgrade issue . . .
I have a "Samba | SOGo | OpenChange" server running in VMware.
I get the following message when running 'apt-get upgrade' --
The following packages have been kept back:
libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind
libpam-winbind libsmbclient libwbclient0 openchangeproxy openchangeserver
python-ldb python-ocsmanager python-samba samba
2012 Jan 14
0
[PATCH] support master user to login as other users by DIGEST-MD5 SASL proxy authorization
Hi Timo,
As http://wiki2.dovecot.org/Authentication/MasterUsers states, currently
the first way for master users to log in as other users only supports
PLAIN SASL
mechanism, and because DIGEST-MD5 uses user name to calculate MD5 digest,
the second way can't support DIGEST-MD5.
I enhance the code to support DIGEST-MD5 too for the first way, please
review
the attached patch against
2024 Jun 14
1
winbind error after startup on Samba member server
On 13.06.2024 20:33, Peter Milesson via samba wrote:
>
>
> On 13.06.2024 17:21, Rowland Penny via samba wrote:
>> On Thu, 13 Jun 2024 16:26:17 +0200
>> Peter Milesson via samba <samba at lists.samba.org> wrote:
>>
>>> Hi folks,
>>>
>>> The last log record from journalctl -xeu winbind directly after
>>> winbind startup is:
2015 Jun 15
1
Samba upgrade issue . . .
Ok Steve,
to be sure..
run :
apt-key adv --keyserver keys.gnupg.net --recv-key 0x810273C4
if not done yet.
add to /etc/apt/source.list.d/openchange.list
deb http://inverse.ca/ubuntu trusty trusty
or
deb http://inverse.ca/ubuntu-nightly trusty trusty
to force the needed packages.
__COPY_PAST_START
cat << EOF >> /etc/apt/preferences.d/preferences-ubuntu-trusty
Package: *
Pin:
2016 Jun 11
0
ldb-tools and ldaps after badlock
On Fri, 2016-06-10 at 19:37 +0200, Stefan Kania wrote:
> Hello everybody,
>
> since the patch for all the badlock bugs it is not possible to access
> a Samba 4 ADDC-database with ldb-tools. Everytime I try it, I get the
> following error:
...
> When I add:
> ----------------------
> tls verify peer = no_check
> ----------------------
> to smb.conf I will get the
2009 Apr 15
3
Postfix, Dovecot SASL and Entourage smtps authentication fails.
Tere.
Recently just migrated from Sendmail 8.14.3 to Postfix 2.5.6 and
switched from Cyrus-sasl 2.1.22 to Dovecot 1.1.13 sasl, all are compiled
from source and I have used Dovecot for a long time, since alpha versions.
Everything worked well for Outlook Express, Outlook and Thunderbird
clients, but Microsoft Entourage 2004 or 2008 clients smtps fails -
"Authentication failed because
2024 Nov 05
1
Login to LDAP from new version FortiClientEMS
W dniu 2.11.2024 o?11:19, Rowland Penny via samba pisze:
>
> If your TLD is '.local', then I take it you missed that it is reserved
> for Bonjour and Avahi, so if Avahi is running on the DC, you should
> turn it off (and everywhere else in your domain).
I am aware of this. The domain was set up almost 20 years ago, at that
time some guides advised not to do anything on the
2015 Jun 15
4
Samba upgrade issue . . .
On 06/15/2015 07:14 AM, Rowland Penny wrote:
> On 15/06/15 11:52, Steve Ankeny wrote:
>> I have a "Samba | SOGo | OpenChange" server running in VMware.
>>
>> I get the following message when running 'apt-get upgrade' --
>>
>> The following packages have been kept back:
>> libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0
2016 Apr 22
0
ldap start_tls to microsoft active directory
I've encountered exact same issue as in this thread below, but I cannot
figure out what the solution is
https://lists.samba.org/archive/samba/2015-February/189012.html
In short, my Samba 4.1.22 used to be a member of the domain, with these
ldap ssl settings in the config:
ldap ssl = start tls
ldap ssl ads = Yes
I've updated it to 4.3.8, and it now cannot talk to the domain, it shows