Directory listing in libsmbclient.so

[Christopher R. Hertel]

> No, workgroup name is not needed in order to handle the authentication,
> but you may want to provide it for trusts when you does not want to access
> a machine using it's default domain/workgroup.

If you are logging into an ntdomain rather than a workgroup, how do you 
specify to which ntdomain you belong?  Does it depend on the server?

If the workgroup/ntdomain is optional, then I would want to take it out 
of the syntax I suggested in my last message.  Thus:

  smb://[user[:passwd]@]server[:port]/service/path/file

The problem with this is that it does not give us the ability to deal with
browsing the available workgroups/ntdomains.  smb:// still gives you the
list of available workgroups/ntdomains, but what do you get when you 
click on one?

I go back to your previous suggestion and suggest:

  smb://[wg|ntd#][user[:passwd]@]server[:port]/service/path/file

so that clicking on a listed workgroup or ntdomain would give you:

  smb://workgroup#/
or
  smb://ntdomain#/

Hmmm... I don't like it.  Mike, Simo?  Other options?

> if you want to access a share on machine A of domain X you need only to
> provide a valid domain X username, but if you want to open the shar as
> user simo of machine A (not user of domain X) you would need to use A\simo
> as username to tell the machine to authenticate the user againts it's own
> sam and not against the domain sam.

That all depends on the auth mechanism of the server.  Again, it comes
down to designing a workable general-purpose syntax for a URI.  It should
not be required that the user know the auth mechanism of the remote
service. 

Chris -)-----

-- 
Christopher R. Hertel -)-----                   University of Minnesota
crh at nts.umn.edu              Networking and Telecommunications Services

    Ideals are like stars; you will not succeed in touching them
    with your hands...you choose them as your guides, and following
    them you will reach your destiny.  --Carl Schultz