smbcli connection using public libs only

Andrew Bartlett abartlet at
Mon Jan 9 00:59:13 MST 2012

On Mon, 2012-01-09 at 08:32 +0100, Stefan (metze) Metzmacher wrote:
> Hi Catalin,
> > I'm trying to figure out the "right" way to open a smbcli connection
> > using only public libraries.
> Please note that the smb_raw_* api is not a supported stable interface,
> it will change in future and hopefully made private again for usage in
> smbtorture only.
> I hope we'll get async (tevent_req based) smb client library for application
> usage in future, which will also support smb2, but it's not there yet.


I'm wondering if a possible approach would be to code up this against
the private interfaces, as a patch to Samba?  

Then, like our bind9_dlz module, we could provide your gvfs plugin
(which could then internally link to any suitable API), and export it
with the stable and public interface.  I would warn that while marked
public, a number of the other APIs you would also need to use
(cli_credentials in particular) are still evolving.

That would avoid some of the challenges of maintaining a supported,
public API broad enough to implement gvfs while still developing Samba.

What do you think?

Andrew Bartlett

Andrew Bartlett                      
Authentication Developer, Samba Team 

More information about the samba-technical mailing list