search for: queryable

...tware all ACL were stored in a database, so that it was possible to quickly find which files one user or group had access to. I'm investigating the possibility of writing ntfs ACL on a database with samba. The module vfs_acl_tdb is able to do this, but values are hashed so that the db is not queryable. Does anyone knows of a way to achieve this? I've had a look at the code of the vfs_acl_tdb module and, for what I understood, the ACL are written both on a tdb and on the filesystem. What's the behaviour of the module then? When I use a software like icacls, to backup ACL, it looks like...

...Pete Biggs <pete at biggs.org.uk> wrote: > On Tue, 2019-02-19 at 14:26 +0000, Pete Biggs wrote: >> >> It's not a web server port - elasticsearch is a database. > > Sorry, that was a bit abrupt - yes, it sort of looks like a web server. It's a bit of both. It is queryable like a database, but it answers requests using HTTP methods. --keith -- kkeller at wombat.san-francisco.ca.us

...; > that it was possible to quickly find which files one user or group > > had access to. > > I'm investigating the possibility of writing ntfs ACL on a database > > with samba. The module vfs_acl_tdb is able to do this, but values > > are hashed so that the db is not queryable. > > Does anyone knows of a way to achieve this? > > Hmmm. tdb is merely a key/value lookup store. Queries on non-keys > have to be done by traversing the whole db I'm afraid. > > You could always change to a sqlite backend if you needed more > indexes. > > >...

...red in a database, so > that it was possible to quickly find which files one user or group > had access to. > I'm investigating the possibility of writing ntfs ACL on a database > with samba. The module vfs_acl_tdb is able to do this, but values > are hashed so that the db is not queryable. > Does anyone knows of a way to achieve this? Hmmm. tdb is merely a key/value lookup store. Queries on non-keys have to be done by traversing the whole db I'm afraid. You could always change to a sqlite backend if you needed more indexes. > I've had a look at the code of the vfs_a...

...it was possible to quickly find which files one user or group >>> had access to. >>> I'm investigating the possibility of writing ntfs ACL on a database >>> with samba. The module vfs_acl_tdb is able to do this, but values >>> are hashed so that the db is not queryable. >>> Does anyone knows of a way to achieve this? >> Hmmm. tdb is merely a key/value lookup store. Queries on non-keys >> have to be done by traversing the whole db I'm afraid. >> >> You could always change to a sqlite backend if you needed more >> indexes....

...ee > > http://www.isc.org/index.pl?/sw/bind/bind-security.php > > for details. > > The version of bind on 6.2, 9.3.3, looks like it is vulnerable (along with > many other versions). It's not particularly an issue for me since my name > servers aren't publicly queryable, but I am curios about how things like > security problems in > src/contrib get handled in FreeBSD. Yes, the FreeBSD Security Team and the FreeBSD BIND maintainer are aware of the issue and are working on fixing it in FreeBSD as soon as possible. More details about the issue can be found a...

On Tue, 2019-02-19 at 14:17 +0000, Laack, Andrea P wrote: > Selinux will not allow connections on other than default http ports. > > semanage port -m -t http_port_t -p tcp 9200 It's not a web server port - elasticsearch is a database. P.

Hi, We have done some investigation. Please find my comment inlined bellow. > > On 14.02.2019. 20:20, Quentin Colombet wrote: >> Hi all, >> >> As much as possible I would rather we avoid any kind of metadata in MIR >> to express the semantic of instructions. >> Instead I would prefer that each back provides a way to interpret what >> an instruction is

Hi, I have a big "name problem" with my internal mail server (10.0.0.152). It is "seen" on the internet through DNAT (213.58.230.27). Also there is a MX record pointing to the machine. Everything works fine from the outside. However i can''t set the mail clients on the lan pointing to the mx record, because this one points to 213.58.230.27 and the firewall