From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Samba with compile option --with-winbind
Date: Wed, 26 Mar 2014 13:00:04 +0100 [thread overview]
Message-ID: <1395835204.19318.37.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <003501cf48e3$2affb190$80ff14b0$@lusch.de>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
Hello Olaf,
compiling Samba with only this option will not do what you expect it to
do. Winbind is already included with the current samba package, but is
not started by default.
In order to authenticate the samba server against a Windows Active
Directory Domain Controller, a lot more things are needed that are
currently NOT included with IPFire.
-Michael
On Wed, 2014-03-26 at 12:04 +0100, Olaf Albrecht wrote:
> Why ist Samba as IPFire package (Pakfire) not compiled with –
> with-winbind so it can authenticate with Active Directory to reach a
> single sign on/passthrou authentication?
>
>
>
> If it is an error how long does it take to get a new Samba package
> over Pakfire?
>
>
>
>
> Ferdinand Lusch GmbH &
> Co. KG
> Im Brocke 11
> 33649 Bielefeld
> Tel: +49 (521) 9417 0
> Fax: +49 (521) 9417 228
> info(a)lusch.de
> www.lusch.de
>
>
> Zweigwerk Buke:
> Industriestraße 21
> 33184 Altenbeken-Buke
> Tel: +49 (5255) 98890 0
> Fax: +49 (5255) 98890
> 50
>
> Kommanditgesellschaft,
> Sitz u. Reg.-Ger.
> Bielefeld HRA 10273
> Komplementär: LUBRA
> Verwaltungsgesellschaft
> mbH,
> Sitz u. Reg.-Ger.
> Bielefeld HRB 30 488
> Geschäftsführer:
> Katharina Lusch,
> Wolfgang Exner
>
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
parent reply other threads:[~2014-03-26 12:00 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <003501cf48e3$2affb190$80ff14b0$@lusch.de>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1395835204.19318.37.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox