Enjoy.
From a very very fast look, it looks like something with file mangling, but IANA
Samba Expert.
baddosdel.cap is against Samba-CVS (From yesterday)
gooddosdel.cap is against my personal W2K workstation.
--
Nir Soffer -=- Exanet Inc. -=- http://www.evilpuppy.org
Father, why are all the
Thank you for your feedback,
the command gives us all Domain-Controllers and the name of the Domain. But
what are the 1C-Adresses ??? -What does 1C mean ?
BTW: We have another problem now: some Workstations get during the first
logon the message: could not connect to domain controller After some
Thank you for your feedback,
the command gives us all Domain-Controllers and the name of the Domain. But
what are the 1C-Adresses ??? -What does 1C mean ?
BTW: We have another problem now: some Workstations get during the first
logon the message: could not connect to domain controller After some
On Mon, Mar 17, 2003 at 11:22:54AM +0100, [EMAIL PROTECTED] wrote:
i tried to compile the current CVS today and found a typo and missing
arguments.
i append a small diff, that fixes these problems..
Hi - someone forgot their janitorial duties with regard to the
smbwrapper support. I've
On Mon, 2003-03-17 at 22:56, Tim Potter wrote:
On Mon, Mar 17, 2003 at 11:22:54AM +0100, [EMAIL PROTECTED] wrote:
i tried to compile the current CVS today and found a typo and missing
arguments.
i append a small diff, that fixes these problems..
Hi - someone forgot their janitorial
Hi !
I have a problem with compiling samba 2.2.8 on rh 7.3 (all
erratas applyed, kernel 2.4.20 with ac2 patch).
When i do rpm -ba samba.spec, i have error:
checking whether struct passwd has pw_age... no
checking for poptGetContext in -lpopt... no
checking whether to use included
Andrew:
Patch to HEAD below -- sorry, should have realized that.
The reason I had to change it was that ads_set_machine_password uses
ads-auth.realm to build the principal name. Should that be
ads-config.realm?
Ken
Ken Cross
Network Storage Solutions
Phone
Hello,
The [Samba] number of groups of NT account causes authentication
problems thread discussed the problem of dealing with NT users,
which are members of more domain global groups than the OS running
Samba can cope with.
Limits do vary, some have 16, or 20, or 32, with some platforms it's
Hello,
I was reviewing the code of del_share_entry function (.../locking/locking.c) that is
suppose
to return the entry deleted when supplied with a ppse pointer. If there are a number
of entries
that satisfy the share_mode_identical criteria (more than one), memdup will be called
more then
BTW, the patch also includes two more lines of output for net ads info
-- the KDC server and server time offset. I find them useful for
helping to automate the join process.
Ken
Ken Cross
Network Storage Solutions
Phone 865.675.4070 ext 31
[EMAIL PROTECTED]
Hello,
I am having problems building Samba 2.2.8 on HP-UX 11.00.
I am using the ANSI C compiler,
/opt/ansic/bin/cc:
LINT A.11.01.25171.GP CXREF A.11.01.25171.GP
HP92453-01 A.11.01.25171.GP HP C Compiler
$ Sep 8 2000 23:13:51 $
My configure line is
CC=cc
Is 3.0 also vulnerable?
Willi Mann
From: Gerald (Jerry) Carter [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: [SECURITY] Samba 2.2.8 available for download
This release provides an important security fix outlined in the
release notes that follow.
On Mon, Mar 17, 2003 at 08:13:15PM +0100, Willi Mann wrote:
Is 3.0 also vulnerable?
3.0 is not released yet. 3.0 alphas are vulnerable, the
SAMBA_3_0 code in CVS is not.
Jeremy.
On Mon, Mar 17, 2003 at 11:22:57PM +1100, Andrew Bartlett wrote:
Yep - I'm about 2 weeks behind on janitorial duties :-(
That's very dangerous. What happens then is someone fixes
it differently in 3.0, and then we have a problem.
Remember, if a fix is obviously applicable to 3.0 it should
Hi!
This patch fixes autogen.sh on systems which have only autoconf-2.53
installed. It makes it simple to add other autoconf versions which might
occur in the future (TESTAUTOCONF/HEADER var). I've only tested it on
RedHat 7.3 with 3.0 branch, so please review it carefully before you
apply
From a quick check of a couple of distributions it looks like winbind is
not included as part of the logon (pam/nss) configuration choices although
users who know what they are doing could manually configure it by hand
editing files after the installation of Samba.
Discounting the esoteric,
Hello all,
This weekend, we upgraded our Samba servers to 2.2.8 (pre3
according to the include/version.h -- CVS synced this past
Saturday afternoon, EDT). I compiled this new release for
the following Solaris/kernel :
Solaris 6 : kernel patch 105181-33
Solaris 7 : kernel patch 106541-23
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i tried a lot of things with the current SAMBA_3_0 today.
everything is working fine, except, the ldapsam_nua passdb backend.
i've all accounts in the ldap tree and i want to provide 2 machines
running FreeBSD. one is used to be the PDC and one
Hi,
I am facing strange problem with Windows-XP
and samba 2.2.7a. Every thing was working just fine
with Win2000, but with WinXP I am not able to see the
list of drivers that I already installed with Win2000.
So if I look at printer property of any printer on samba server
(from My Network
On Tue, 2003-03-18 at 08:01, [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i tried a lot of things with the current SAMBA_3_0 today.
everything is working fine, except, the ldapsam_nua passdb backend.
i've all accounts in the ldap tree and i want to provide
sorry to be stupid on cvs -- its always worked as documented on the
web site.. but now its not.
after I do
$cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot login
$ cvs update -d -P
? source/myconf.sh
cvs server: Updating .
P Manifest
cvs [update aborted]: cannot open .new.Manifest: Permission denied
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
While looking at HEAD / ldapsam_delete_sam_account a bit closer I
found that we completely delete the user. Would it not be better just
to remove the samba-specific attributes and let the 'delete user
script' do the rest? Hmm. srv_samr_nt.c works
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Here's my first attempt at putting the group mapping into ldap. It
should apply to HEAD.
Comments? Especially the schema might be discussed, this is my very
first attempt at LDAP schema design.
Volker
P.S.: smbgroupedit *really* needs to be
On Mon, Mar 17, 2003 at 03:01:38PM -0700, David Bear wrote:
sorry to be stupid on cvs -- its always worked as documented on the
web site.. but now its not.
after I do
$cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot login
$ cvs update -d -P
Why don't you checkout the source tree first,
hello volker,
On Mon, Mar 17, 2003 at 11:08:09PM +0100, Volker Lendecke wrote:
Hi!
While looking at HEAD / ldapsam_delete_sam_account a bit closer I
found that we completely delete the user. Would it not be better just
to remove the samba-specific attributes and let the 'delete user
3) Could winbind easily handle some of the nss lookups via ldap ala rfc
2307 schema (if it matters anymore - it is just an experimental RFC) as a
While there are probably more domain controllers than RFC 2307-compliant
LDAP servers, it is the de facto LDAP nameservice schema for the UNIX
On Mon, Mar 17, 2003 at 11:38:40PM +0100, Rafal Szczesniak wrote:
On Mon, Mar 17, 2003 at 03:01:38PM -0700, David Bear wrote:
sorry to be stupid on cvs -- its always worked as documented on the
web site.. but now its not.
after I do
$cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot login
While there are probably more domain controllers than RFC 2307-compliant
LDAP servers, it is the de facto LDAP nameservice schema for the UNIX
platform, and is thus unlikely to disappear overnight. Many large
organisations have deployed this schema (they are our customers).
I agree, but was
I agree, but was thinking about ease of use, and longer term whether we
could have the
logon/caching/performance intensive UID/GID caching leveraged by the four
and five
main alternatives (winbind already supports two) and whether the caching
code for
a particular pam/nss daemon was already
Folks
I know 2.0.10 is *old*, but we are still using it internally (we have
simple needs and it provides them nicely). Are there patches available
that we can apply to the 2.0.10 code that will address the latest security
vul? It mentioned in the advisory to ask here for th
I know we have
On 17 Mar 2003, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
checking whether to use included popt... ./popt
checking configure summary... configure: error: summary failure.
Aborting config
Have a look in config.log. If you can't work out what's wrong from
that, post the *relevant*
For developer mode, this seems to be the same as safe_strcpy: we
clobber the specified region at runtime. Otherwise, it skips the
static CHECK_STRING_SIZE call.
I think this is meant to allow you to call it passing the address of
an array whose size is less than the maxlength passed to
On Tue, Mar 18, 2003 at 04:11:23PM +1100, Martin Pool wrote:
For developer mode, this seems to be the same as safe_strcpy: we
clobber the specified region at runtime. Otherwise, it skips the
static CHECK_STRING_SIZE call.
I think this is meant to allow you to call it passing the address of
On Tue, 2003-03-18 at 09:08, Volker Lendecke wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
While looking at HEAD / ldapsam_delete_sam_account a bit closer I
found that we completely delete the user. Would it not be better just
to remove the samba-specific attributes and let
Hi, Guenther!
On Tue, Mar 18, 2003 at 12:17:21AM +0100, Guenther Deschner wrote:
no. but SuSE ships a diff for 2_2 for quite some time now with another
smb.conf option that helps users not to delete their posix-account by
coincidence.
Why don't you use the make_a_mod function?
Volker
35 matches
Mail list logo
