** Changed in: cloud-archive/ocata
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1744882
Title:
Add SPEC_CTRL and IBRS changes
To manage notif
** Bug watch added: Samba Bugzilla #13376
https://bugzilla.samba.org/show_bug.cgi?id=13376
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=13376
Importance: Unknown
Status: Unknown
** Changed in: samba (Ubuntu)
Status: Incomplete => Triaged
** Changed
Can you elaborate on how this 18.04 machine is supposed to authenticate
users and give them access or not to a share, since it's not part of the
AD realm, at least according to smb.conf? In the meantime I'll check
with upstream.
--
You received this bug notification because you are a member of Ub
Ok, I can reproduce this with a simple "smbclient -L localhost -N" and
this smb.conf:
[global]
dns proxy = No
domain master = No
kerberos method = secrets and keytab
local master = No
log file = /var/log/samba/log.%m
map to guest = Bad User
Was this 18.04 box a fresh install of samba 4.7.6, or did you at some
point have 4.7.4 or earlier and upgrade?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1761737
Title:
[bionic] samba
The smb.conf file for the 18.04 box shows it as being a standalone
server, not a domain member. Is that expected? Are you managing its
users locally via smbpasswd?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to samba in Ubuntu.
https://bugs
