Netapi32 ??

[Martin Wilck]

The app I am trying to port with winelib makes heavy use of calls to
the netapi32 DLL to check for permissions, etc.

I just took a glance over the spec file and found it consists mainly of
stubs.

Is anybody (Mike?) currently working on netapi32, are there plans to
implement larger parts, what are the main problems?

I guess this points towards the general Wine/Samba integration that Mike
has been talking about earlier...

Grateful for any hints,
Martin

[Uwe Bonnes]

> > > > > "Martin" == Martin Wilck  writes:

Martin> The app I am trying to port with winelib makes heavy use of
    Martin> calls to the netapi32 DLL to check for permissions, etc.

Martin> I just took a glance over the spec file and found it consists
    Martin> mainly of stubs.

Martin> Is anybody (Mike?) currently working on netapi32, are there
    Martin> plans to implement larger parts, what are the main problems?

Martin> I guess this points towards the general Wine/Samba integration
    Martin> that Mike has been talking about earlier...

In my understanding, netapi only chunks down to lower lever driver, like
netbios etc. If the driver of your application end in doing real hardware
access or strange protocolls, things will get fishy...

Bye

[Martin Wilck]

Am Mon, 2002-09-16 um 18.59 schrieb Uwe Bonnes:
> In my understanding, netapi only chunks down to lower lever driver, like
> netbios etc. If the driver of your application end in doing real hardware
> access or strange protocolls, things will get fishy...

What my app wants is mostly network authorization issues, i.e. calls
like NetLocalGroupGetMembers(), NetUserGetLocalGroups(), etc.
Yes I assume this will usually work through Netbios (that's why I think
it may go in the Samba direction), but I'm not quite sure yet.

I don't think it's about direct hardware access & strange protocols.

Martin

[Andriy Palamarchuk]

--- Martin Wilck 
wrote:
> The app I am trying to port with winelib makes heavy
> use of calls to
> the netapi32 DLL to check for permissions, etc.
>
> I just took a glance over the spec file and found it
> consists mainly of
> stubs.
>
> Is anybody (Mike?) currently working on netapi32,
> are there plans to
> implement larger parts, what are the main problems?
>
> I guess this points towards the general Wine/Samba
> integration that Mike
> has been talking about earlier...

I'm now working to implement some netapi32 calls.
My implementations use information, provided by Wine
or give some dummy values.
Do you think this will be enough for your application?
You can give me the list of calls your application
uses - I'll give preference to implementing them.

Sure the right approach would be to integrate it with
Samba but I was not going to do it right now.

Andriy,
Boston, MA, USA

As an employee of an oil company, let me assure you
that nothing, and I mean NOTHING scares a big company
more than a noisy, smelly, obnoxious, disaffected
pressure group.
Now go away and chain yourself to someone important's
front door.

TheRegister. Unknown

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

[Martin Wilck]

Am Mon, 2002-09-16 um 20.43 schrieb Andriy Palamarchuk:
> I'm now working to implement some netapi32 calls.
> My implementations use information, provided by Wine
> or give some dummy values.
> Do you think this will be enough for your application?

Hmm - it's about identification and access right verification.
Currently I rather tend to replace all this by "native unix"
verification. I actually don't think it's a good idea for my app to
bypass the Unix system.

In this context, one idea would be to simply route requests like these
to Unix services like PAM. There may even be a samba Authorization
service for PAM installed. That way it might actually be possible to map
authorization issues like this correctly from wine to e.g. a PDC, but
through the native Unix interface, and without creating a Samba+Wine
"monster" app. This is far future of course.

What do you think?
> You can give me the list of calls your application
> uses - I'll give preference to implementing them.

I'll try to make a list.

Thanks, Martin

[Andriy Palamarchuk]

--- Martin Wilck 
wrote:
> In this context, one idea would be to simply route
> requests like these
> to Unix services like PAM. There may even be a samba
> Authorization
> service for PAM installed. That way it might
> actually be possible to map
> authorization issues like this correctly from wine
> to e.g. a PDC, but
> through the native Unix interface, and without
> creating a Samba+Wine
> "monster" app. This is far future of course.
>
> What do you think?

Agree with your idea.
I'll start to look into it later.

Andriy
Boston, MA

As an employee of an oil company, let me assure you
that nothing, and I mean NOTHING scares a big company
more than a noisy, smelly, obnoxious, disaffected
pressure group.
Now go away and chain yourself to someone important's
front door.

TheRegister. Unknown

__________________________________________________
Do you Yahoo!?
Yahoo! News - Today's headlines
http://news.yahoo.com

[Martin Wilck]

Am Die, 2002-09-17 um 14.47 schrieb Andriy Palamarchuk:
> Agree with your idea.
> I'll start to look into it later.

With winbind running (and the NSS switch properly configured), you can
use standard glibc calls like getpwnam()
and they'll return what you want. Great stuff!

Martin

[Martin Wilck]

Am Mon, 2002-09-16 um 20.43 schrieb Andriy Palamarchuk:
> Sure the right approach would be to integrate it with
> Samba but I was not going to do it right now.

As I said in another message, I think the Samba component (at least for
authentication issues) should be independent of wine and accessed e.g.
through PAM.

That would be cleaner and much easier, given that pam_winbind is
available on recent samba releases.

Martin