search for: encrytped

Hi here! How libvirt virsh solves attachment of hot plug/unplug encrytped USB devices?? We've no problems attaching full encrypted(LUKS) usb disk or memory pen to guest using virsh attach-disk command. But not working using virsh attach-device to use USB pass-through and hot plug/unplug features. USB pass-through works properly without encryption. Any procedure to...

...Not that this helps....I have no clue what I am doing on the Windows side. We use the SAME smb.conf file with a few changes. The workgroup = 2Kdomain, the netbios name is different. Both servers were setup for: [global] workgroup = <nt or 2k domain> encrypted passwords = yes update encrytped = yes password server = <one or two> passwd chat debug = yes log level = 5 log file = /var/adm/samba.log name resolve order = host deadtime = 10 [homes] path = /home/%u read only = No browseable = No All other shares just like homes...very simple. What happens is that we...

...e level as users/admins see things. The admin can control wither users can enable encryption or not by delegating (or not) the "encryption" and "keytype" properties. So there is no need to use the pool wrapping key (ie require the kek to be available) to restrict creation of encrytped datasets. If the admin doesn''t want encryption in any dataset delegated to a user then don''t delegate those properties and ensure they are inherited as encryption=off. We need to be able to provide key change for keytype=dataset as well. That means that the actual encryption...

...e level as users/admins see things. The admin can control wither users can enable encryption or not by delegating (or not) the "encryption" and "keytype" properties. So there is no need to use the pool wrapping key (ie require the kek to be available) to restrict creation of encrytped datasets. If the admin doesn''t want encryption in any dataset delegated to a user then don''t delegate those properties and ensure they are inherited as encryption=off. We need to be able to provide key change for keytype=dataset as well. That means that the actual encryption...

I'm a bit confused on several points of the security infrastructure of Samba. First, and simplest, why (and is it necessary) do we need to keep a smbpasswd file when the Linux/Unix passwd file could be suffice? I like the idea of mapping particular users to a given UNIX account via the username map option, but I see no reason in specifying a separate password file for these same UNIX users.