First of all thanks everybody for the feedback.
It seems that Wine/Samba integration will not be a solution for general
Wine RPC, at least not in the short term.
However I have determined the functionality I need and I think most of
it can be implemented on top of existing winbind functionality
Am Mit, 2002-09-25 um 19.38 schrieb Richard Sharpe:
I do not think that libsmbclient is the right way to do this. I think that
the correct way is to make the various Samba client RPC libaries available
as separate DSOs so that clients can make dirrect use of what they need.
Then the wine
Because DCE/RPC is *horrible* ? :-) :-). If you need a new
RPC protocol please use ONC/RPC/NDR not DCE :-).
I agree, I think I've grown a few gray hairs from DCE. I guess
the argument in favour of it depends on how similar the kinds
of lookups WINE needs to make are to existing, implemented,
- is the winbind team willing to standardize the protocol, or at least
ensure backward compatibility in future versions?
Rather than inventing new protocols, why not just use DCE RPC over domain
sockets or TCP/IP?
The only catch is that you need a DCE RPC client library. We're using the
On Fri, Sep 27, 2002 at 12:50:57AM +1000, Luke Howard wrote:
- is the winbind team willing to standardize the protocol, or at least
ensure backward compatibility in future versions?
Rather than inventing new protocols, why not just use DCE RPC over domain
sockets or TCP/IP?
The
Tim Potter wrote:
On Thu, Sep 26, 2002 at 01:47:38PM +0200, Martin Wilck wrote:
To initiate this process we'd only need a standardized protocol for
the socket communication. Andrew said that doesn't exist and won't with
regard to winbind. I'd like to focus the discussion in this
On Wed, 25 Sep 2002, Rafal Szczesniak wrote:
On Wed, Sep 25, 2002 at 03:06:05PM +0200, Martin Wilck wrote:
Am Mit, 2002-09-25 um 00.55 schrieb Andrew Bartlett:
As to unicode, I
have designated one call as being in utf8, to cope with external
interaction, so it's possible things
On Wed, Sep 25, 2002 at 03:06:05PM +0200, Martin Wilck wrote:
Am Mit, 2002-09-25 um 00.55 schrieb Andrew Bartlett:
As to unicode, I
have designated one call as being in utf8, to cope with external
interaction, so it's possible things can happen here.
What matters to wine is that if a
I started thinking about other options when I found the wbinfo -n
call. AFAIK there is no way to obtain equivalent info through PAM/NSS,
simply because these APIs have no concept of a SID. Obviously apart from
the SID there is a lot more information to gather from a PDC. I have not
digged deeply
On Thu, Sep 26, 2002 at 03:08:29AM +0930, Richard Sharpe wrote:
On Wed, 25 Sep 2002, Rafal Szczesniak wrote:
Seems like you'd like to see one more library as winbind's companion.
However, if libsmbclient is licensing stumbling block, then similar
situation may happen with such winbind's
Am Mit, 2002-09-25 um 00.55 schrieb Andrew Bartlett:
Firstly, it's good to see that winbind is starting to get some interest
:-)
I have been ignoring it so far, but in the context of the current
inquiries I tried it out and was impressed :-)
Secondly, don't fall into the trap squid (with
Hello,
There has been a discussion on wine-devel about using winbind
for purposes like user authorization, retrieving user and group
information, and more.
It seemed reasonable to use PAM and NSS for the basic lookups and
leave it to the sysadmin to configure these services to use winbind
12 matches
Mail list logo
