search for: _locally_

On Fri, 17 Feb 2017 07:58:58 +0100 Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > Am 16.02.2017 um 17:27 schrieb Rowland Penny via samba: > > > However, SYSTEM is used in sysvol and Windows expects it. > > Clients, who are accessing the share, do not require it to be set on > the local filesystem the share uses on the server, because SYSTEM is > a local

On Sat, 18 Feb 2017 00:28:14 +0100 Marc Muehlfeld <mmuehlfeld at samba.org> wrote: > > Yes, because > 1.) It might be necessary _locally_ on the Windows DC > because some _local_ services (e. g. Virus scanners, > etc) may access the files _locally_ _on the DC itself_. > However if anything on the client (the OS or a user) > would access the share using the SYSTEM privilege, > then "full co...

Am 17.02.2017 um 10:28 schrieb Rowland Penny via samba: > So, I give you a link to a Microsoft page that shows what accounts are > required for the profiles share and you choose to ignore it ???? Yes, because 1.) It might be necessary _locally_ on the Windows DC because some _local_ services (e. g. Virus scanners, etc) may access the files _locally_ _on the DC itself_. However if anything on the client (the OS or a user) would access the share using the SYSTEM privilege, then "full control" is surely not...

Am 18.02.2017 um 10:50 schrieb Rowland Penny via samba: >> Yes, because >> 1.) It might be necessary _locally_ on the Windows DC >> because some _local_ services (e. g. Virus scanners, >> etc) may access the files _locally_ _on the DC itself_. >> However if anything on the client (the OS or a user) >> would access the share using the SYSTEM privilege, >>...

...ows machine is where the SYSTEM account is usually used. If the local SYSTEM Account tries to access a network resource, it uses the machine account to authenticate. That's why it is not necessary to add SYSTEM to the file system ACLs on a Samba share: SYSTEM is just an account that exists _locally_ and is not used when connecting to network resources. If you have anything (a service, a task job, etc.) running on your _local_ computer that uses the SYSTEM account, then SYSTEM must be of course added to the local file system ACLs if this task, etc. should be able to access _local_ files....

On Thu, 16 Feb 2017 07:30:03 +0100 Marc Muehlfeld via samba <samba at lists.samba.org> wrote: > > On Windows, the SYSTEM account is used by services on the local host > (in your case, the local host is your Samba server). For example, > virus scanners might use it to get access to all files. However, > there is nothing on your Samba server that uses the SYSTEM account. >

raf wrote: > Warlich, Christof wrote: > > ... > > I want to be able to ssh to all internal hosts that live in the internal.sub.domain.net, > > i.e. that are only accessible through the internal.sub.domain.net jumphost without > > having to list each of these hosts somewhere, as they may frequently be added or > > removed from the internal domain and without being

..." key_file = "/sec/ssl/libvirt/client.EC.key.pem" cat /etc/libvirt/virtproxyd.conf ca_file = "/sec/ssl/CA/CA.CHAIN.crt.pem" cert_file = "/sec/ssl/libvirt/server.EC.crt.pem" key_file = "/sec/ssl/libvirt/server.EC.key.pem" On attempt to first _locally_ connect, virsh -c test:///default list sysinfo Id Name State ---------------------- 1 test running virsh -c test:///default sysinfo <sysinfo type='smbios'> <bios> <entry name='vendor'>LENOVO</entry> <entry name='ve...

...the SYSTEM account is usually used. If the local SYSTEM Account > tries to access a network resource, it uses the machine account to > authenticate. > > That's why it is not necessary to add SYSTEM to the file system ACLs on > a Samba share: SYSTEM is just an account that exists _locally_ and is > not used when connecting to network resources. > > If you have anything (a service, a task job, etc.) running on your > _local_ computer that uses the SYSTEM account, then SYSTEM must be of > course added to the local file system ACLs if this task, etc. should be > able...