On Sun, 22 Feb 2026 14:06:54 +0100, Hiltjo Posthuma wrote:
> On Sat, Feb 21, 2026 at 08:17:06PM +0100, Pascal Stumpf wrote:
> > On Sat, 21 Feb 2026 19:02:49 +0000, Stuart Henderson wrote:
> > > is there any point keeping usmb if we have this? (not sure of current 
> > > development status of usmb, I'm geoblocked from repo.or.cz)
> > 
> > Not really.  Maybe susmb should use readpassphrase(3) instead of an env
> > var for the password though before we use it as the upgrade path for
> > usmb.
> > 
> > > -- 
> > >   Sent from a phone, apologies for poor formatting.
> > > 
> > > On 21 February 2026 16:29:05 Pascal Stumpf <pascal@stumpf.co> wrote:
> > > 
> > > > susmb lets you mount SMB/CIFS shares via FUSE, in the vein of the
> > > > Map Network Drive functionality in Windows.
> > > >
> > > >
> > > > This is a fork of usmb, most notably adding privdrop and unveil(2), and
> > > > getting rid of the XML config file.  Patches from sysutils/usmb have
> > > > also been incorporated.
> > > 
> > > 
> 
> Thanks for the feedback,
> 
> I just added back support for reading the password from the tty:
> 
> https://git.codemadness.org/susmb/commit/eb8f06e5e0f3dfc37d223025c6a43c99b963c2ef.html

Thanks!

> Note that the password is kept in memory during run-time.  I'm not sure
> currently how to make this more secure or improve privdropping (for example
> currently it only uses unveil and not pledge), because of the Samba and FUSE
> layer. If you have ideas, please let me know.

Well, unveil() is already a huge improvement, and while you can try out
which pledges would be needed with Samba, it might well turn into a 
"kitchen sink" type of pledge.  I wouldn't worry too much.

Updated port attached.

> -- 
> Kind regards,
> Hiltjo

• susmb.tgz (2K)