On 03/05/2013 10:13 PM, Matthew Barr wrote:
>
> On Mar 5, 2013, at 9:15 AM, Rob Crittenden wrote:
>
>> Артур Файзуллин wrote:
>>> What rule must be present for replica to work? :) (in order to remove
>>> allow-all rule)
>>> I mean may be there is somewhere a guide to write rules for strict
>>> a
On Mar 5, 2013, at 9:15 AM, Rob Crittenden wrote:
> Артур Файзуллин wrote:
>> What rule must be present for replica to work? :) (in order to remove
>> allow-all rule)
>> I mean may be there is somewhere a guide to write rules for strict
>> allows?
>
> During the installation we check that commu
Артур Файзуллин wrote:
What rule must be present for replica to work? :) (in order to remove
allow-all rule)
I mean may be there is somewhere a guide to write rules for strict
allows?
During the installation we check that communication works between the
two servers, so ssh is needed between ma
What rule must be present for replica to work? :) (in order to remove
allow-all rule)
I mean may be there is somewhere a guide to write rules for strict
allows?
В Пт., 30/11/2012 в 13:24 -0500, Rob Crittenden пишет:
> Natxo Asenjo wrote:
> > hi,
> >
> > the default hbac rule 'allow_all' is nice fo
Natxo Asenjo wrote:
hi,
the default hbac rule 'allow_all' is nice for testing, but for a
production environment I am not so sure ;-)
We do not want our users getting a shell in our kdc servers or in the
database servers for instance. We want them to use the postgresql
service, but not login the
hi,
the default hbac rule 'allow_all' is nice for testing, but for a
production environment I am not so sure ;-)
We do not want our users getting a shell in our kdc servers or in the
database servers for instance. We want them to use the postgresql
service, but not login the database server with