Displaying 20 results from an estimated 1000 matches similar to: "Samba 3.0 + OpenLDAP 2.1 Saga (LDAP Attacks!)"
2002 Aug 01
5
Authenticate against NT Domain Group Membership
Hola folks,
How do I configure a share under Samba 2.2 using DOMAIN security to allow
all members of a specified NT domain group access to a particular share?
For example, something like:
[test]
comment = Test Share
path = /mnt/share/test
nt group = Nice-users, Wonderful Users
Where Nice-users and Wonderful Users are NT domain groups? So if User X is
a member of Nice-users, she would be
2002 Aug 01
5
SUQ: Share permissions
After parsing through the various bits of available documentation, I'm
forced to bow before the group and ask the following Silly User Question:
While I can create and set NT ACLs on files/folder, anything in the root of
the share can be deleted by any user who has access to that share. I've
munged something in my file permissions. What /should/ the file permissions
for a root share
2004 Feb 08
3
samba PDC and BDC with ldap master and slave backend
Hi all !
In the samba-Howto, i was looking on informations on how to set up
both a samba PDC and a samba BDC controller with ldap backend.
I can read:
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Do not install a Samba PDC on a OpenLDAP slave server...
Possible PDC/BDC plus LDAP configurations include:
. PDC -> LDAP master server, BDC -> LDAP slave server.
2003 Dec 23
4
Trying to use LDAP: Failed to bind to server: Invalid Credentials
I'm using RedHat 9 and Samba 3.01rc2. I'm working through the Samba Howto on LDAP but I've no experience of LDAP and I'm struggling to understand what is needed. At the moment when I try to change or set a password with smbpasswd, I get the message "failed to bind to server with dn = etc: Invalid credentials".
So can someone clarify any of these points for me.
1. About
2006 Feb 16
1
Documentation error?
Hi,
I am setting up a fileserver in an AD domain, using Samba 3.0.21b under Solaris 9. An Openldap server (version 2.3.17) is used fot the idmap backend.
Following the Samba HOWTO Collection, chapter 6, I used the statement
ldap idmap suffix = ou=idmap,dc=uppsala,dc=se
in my smb.conf. This doesn't work. When starting winbindd I get the following in the log:
[2006/02/15 10:31:14, 3]
2004 Feb 06
0
FW: Out of Office AutoReply: IPFIREWALL_DEFAULT_TO_ACCEPT becomes def ault to deny
Sigh?
_____
Van: Sorisio, Chris [mailto:ChrisSorisio@PeakTechnical.com]
Verzonden: vrijdag 6 februari 2004 15:56
Aan: Gogh, Ruben van
Onderwerp: Out of Office AutoReply: IPFIREWALL_DEFAULT_TO_ACCEPT becomes def
ault to deny
I will be out of the office until February 9th, 2004. Please contact Paul
DeFloria at 412.825.4772 if you require an immediate response.
2009 Apr 10
2
Some questions about Samba and LDAP
Hello,
I have been using Samba for years (login onto the PC, files and
printers sharing) and since recently I have a LDAP server running and
serving authentication to few Unix systems (mail, web, Zope, ssh,
etc.)
Now that I set-up a new server to use with Samba, I would like to
integrate Samba into the existing LDAP.
All the doc I could find so far is about creating a LDAP service from
scratch
2009 Aug 28
4
Ether Saga Online Error??? Help!!!
Hi, i don't know a lot about linux. But i wanted to play Ether Saga Online...
Anyways, When i ran Launcher.exe
Code:
wine Launcher.exe
2011 Nov 11
2
Lost Saga / Rusty Hearts compatibility
Hello everyone,
I'm a big fan of Lost Saga but despite we can finally use the launcher and update the game, it'll still not start because of X-trap (like Rusty Hearts).
I read that Wine's developers doesn't want to solve the problem because of privacies problems, but personally I don't care that much [Wink]
If they want to take informations about my computer (and do we know
2003 Oct 26
0
The saga continues
Shorewall 1.4.7c is now available and continues the saga with
"<zone>_frwd" chains.
My apologies for this mess....
-Tom
--
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep@shorewall.net
2011 Aug 15
0
Ongoing VM saga ....
.... I have a 64-bit CentOS 5.6 VM running on a 64-bit FC-14 host. I was
originally using the stock NAT networking on the guest, which could
access the host, but nothing else on the network. I eventually found
some links on how to setup routed networking on the guest using a
specifically setup bridge. I followed the example a bit too closely,
bridging my eth0 interface, which is the one I
2011 Aug 15
0
The saga continues ....
.... I have a 64-bit CentOS 5.6 VM running on a 64-bit FC14 host.
Actually, I *HAD* a 64-bit CentOS 5.6 VM :-) .... After a read of the
virt-install man page, I concluded that I could lose the current VM (but
*NOT* its HDD image) & recreate it fairly easily w/ the right combo of
arguments to virt-install. The proceedings:
[root at Q6600:/etc, Mon Aug 15, 04:30 PM] 1163 # virsh list
2010 Jul 26
2
[LLVMdev] Win32 COFF Support patch 5 (the final patch in the saga!)
Attached is the 5th and final patch of the beginning of COFF support
for MC. It simply makes the X86 backend use it on Win32 targets and
tests it.
- Michael Spencer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ms-coff-patch-5.patch
Type: application/octet-stream
Size: 23435 bytes
Desc: not available
URL:
2010 Jul 26
0
[LLVMdev] Win32 COFF Support patch 5 (the final patch in the saga!)
On 26 July 2010 04:35, Michael Spencer <bigcheesegs at gmail.com> wrote:
> Attached is the 5th and final patch of the beginning of COFF support
> for MC. It simply makes the X86 backend use it on Win32 targets and
> tests it.
>
>
You probably want to add Cygwin and MinGW32 Triples as well :-
case Triple::Win32:
+ case Triple::Cygwin:
+ case Triple::MinGW32:
return
2010 Jul 26
0
[LLVMdev] Win32 COFF Support patch 5 (the final patch in the saga!)
On 26 July 2010 18:08, Michael Spencer <bigcheesegs at gmail.com> wrote:
> On Mon, Jul 26, 2010 at 12:04 PM, Aaron Gray <aaronngray.lists at gmail.com>
> wrote:
> > You probably want to add Cygwin and MinGW32 Triples as well :-
> > case Triple::Win32:
> > + case Triple::Cygwin:
> > + case Triple::MinGW32:
> > return new
2011 Jul 12
1
CentOS 6: the ongoing saga
We'll ignore that the group name for KDE changed, and so, since we had it
on the same line as X, neither was installed.
However, more of an annoyance: to get nfs working, I had to install:
pam-krb5
ncsd
then fix /etc/init.d/autofs (when I did a service restart, it told me
automount was running, and did not stop it), then after some research,
found I had to manually start rpcbind, *then*
2005 Aug 10
0
The CDex and Flac saga continues
Hello all,
I seem to be in a bit of a bind. Below is the email which I sent to the
list a while back. I wrote the vast majority of my CD collection to Flac
and checked them with the Flac test (the -t option of Flac), they played
fine and all seemed wonderful.
Sadly life is no longer roses and chocolates. Now as I come to rip the
whole lot to Vorbis files, Oggenc is spewing an error that the
2005 Aug 13
0
The CDex and Flac saga continues
At 01:42 AM 8/13/2005, you wrote:
> > It would actually be easier to rerip all your CDs using EAC. I rip to
> > ogg vorbis with EAC and it comes out fine. I can give you a website URL
> > that will give you the info on how to setup EAC to use ogg vorbis. And I
> > use -q 8 so they sound good.
>
>Thanks for the suggestion, Jon, but I would rather not re-rip them. I
2010 Jul 26
2
[LLVMdev] Win32 COFF Support patch 5 (the final patch in the saga!)
On Mon, Jul 26, 2010 at 12:04 PM, Aaron Gray <aaronngray.lists at gmail.com> wrote:
> You probably want to add Cygwin and MinGW32 Triples as well :-
> case Triple::Win32:
> + case Triple::Cygwin:
> + case Triple::MinGW32:
> return new WindowsX86AsmBackend (T);
> Aaron
Can someone test this on those platforms? That change would effect
quite a few people.
-
2003 Nov 08
1
Samba 3 doesn't compile - the saga continues...
Please see my post from 24 hours ago for the background on my efforts to get
Samba to run.
I received instructions to modify include/includes.h to change the #include
<compat.h> to #include <compat_ap.h>. Needless to say, this solved nothing
other than a bunch of harmless warnings. It also caused a different warning to
spew forth eternally from gcc, and more importantly, it