search for: focued

Hey folks, I've been experimenting with native NBD live migration w/ TLS and have a couple of questions. 1) It appears that in some cases modified default_tls_x509_cert_dir from qemu.conf is not respected, seems like virsh always expects a default location and does not check default_tls_x509_cert_dir: virsh # migrate vm1 qemu+tls://ratchet.lan/system --live --persistent --undefinesource

...ttings for the 'migration' TLS environment. I don't think we have a setting to always force migration using TLS and it might not fit well with the design of the --tls flag (as it would be impossible to disable it then). You can file an feature request for it though. As it is a security focued setting and defaulting to encryption may be worthwhile in many scenarios. Note that in somewhat old libvirt versions there was a bug that that the NBD connection used for the disk migration was not encrypted. This is now addressed and newer libvirt will not allow migration from/to such libvirt: h...

Hai, I commented below. P.s. @Rowland, i dont believe this is a sssd problem but a old bug in samba. > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Daniel Carrasco via samba > Verzonden: dinsdag 24 oktober 2017 19:30 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Using GPO to mount shares on Linux > >

On 25/10/2020 20:37, Sonic wrote: > The reset allowed the current GPO to take effect, but right after > adding a new GPO (just named it, no editing, or linking) the > sysvolcheck fails: > # samba-tool ntacl sysvolcheck > ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception > - ProvisioningError: DB ACL on GPO directory >

> It's needed after every GPO addition and edit. There must be a root > cause to hunt down somewhere. Or is it a bug in 4.13.0 ? Yes, and no. Yes, its a bug. No, in my opionion its an old setting thats just needs some updating. Try this. samba-tool ntacl set "O:LAG:BAD:P(A;OICI;0x001f01ff;;;BA)(A;OICI;0x001200a9;;;SO)(A;OICI;0x001f01

Hai, I did a re-read of you thread. First. If you use smblcient, with a samba installed, use -s /path/alternative/smbclient.conf If i did read it correct. Your connecting from xUbuntu (samba version ??) to (debian8) samba 4.2 member How did you join the xUbuntu? https://docs.pagure.org/SSSD.sssd/users/ad_provider.html Like this setup? ^^^ > This setup is working as expected (some