Re: security.conf and FreeBSD jails

[Ekkehard 'Ekki' Gehm]

Ahoi!

[SOLVED]

OK. That fixed it... as I use ssh-auth the homedir of amanda is owned by
the amanda user not root. FreeBSD ports default to the etcdir wich is
the home-dir... Anyways... solved... Thx!

Ekki


Am 07.06.2017 um 18:21 schrieb Jean-Louis Martineau:
> It is hardcoded when amanda is configured (--with-security-file).
> You can find the value with: amgetconf build.security_file
> You must reconfigure amanda if you want to change it.
>
> Jean-Louis
>
> On 07/06/17 12:13 PM, Ekkehard 'Ekki' Gehm wrote:
>>
>> Ahoi!
>>
>> is there a config option to tell amanda where look for it? Because
>> moving the file to /etc/ gives the following:
>>
>> ERROR: hostname: [Can't get realpath of the security file
>> '/usr/local/etc/amanda/security.conf': No such file or directory]
>>
>> Ekki
>>
>>
>> Am 07.06.2017 um 17:47 schrieb Jean-Louis Martineau:
>>> The complete path to security.conf must be owned and writable only by
>>> the root user
>>>
>>> $ man amanda-security.conf
>>>
>>> That's why it is by default in /etc and not in /etc/amanda which
>>> must be
>>> writable by the amanda user.
>>>
>>> Jean-Louis
>>>
>>> On 07/06/17 11:37 AM, Ekkehard 'Ekki' Gehm wrote:
>>> > Ahoi!
>>> >
>>> > I ran into an issue with the last update. Apparently amanda doesn't
>>> > like my security.conf. And I do not know why. Any hints?
>>> > The client is a FreeBSD Jail whilst the server is a FreeBSD Host...
>>> >
>>> >
>>> > amcheck output:
>>> >
>>> > ERROR: hostname: [/s/var/db/amanda
>>> (/usr/local/etc/amanda/security.conf)
>>> > is not owned by root]
>>> >
>>> > But:
>>> > -rw-r--r-- 1 root wheel 2 Jun 7 17:12:55 2017 security.conf
>>> >
>>> > Version of amanda client: amanda-client-3.3.9,1
>>> >
>>> > Version of amanda server: amanda-server-3.3.6_5,1
>>> >
>>> > Thx in advance :-)
>>> >
>>> >
>>> > Ekki
>>> >
>>>
>>>
>>> *Disclaimer*
>>>
>>> This message is the property of *CARBONITE, INC.*
>>>  and may contain confidential or
>>> privileged information.
>>>
>>> If this message has been delivered to you by mistake, then do not
>>> copy or deliver this message to anyone. Instead, destroy it and
>>> notify me by reply e-mail.
>>>
>>
>
>
>
> *Disclaimer*
>
> This message is the property of *CARBONITE, INC.*
>  and may contain confidential or privileged
> information.
>
> If this message has been delivered to you by mistake, then do not copy
> or deliver this message to anyone. Instead, destroy it and notify me
> by reply e-mail.
>

Re: security.conf and FreeBSD jails

[Jean-Louis Martineau]

It is hardcoded when amanda is configured (--with-security-file).
You can find the value with: amgetconf build.security_file
You must reconfigure amanda if you want to change it.

Jean-Louis

On 07/06/17 12:13 PM, Ekkehard 'Ekki' Gehm wrote:


Ahoi!

is there a config option to tell amanda where look for it? Because 
moving the file to /etc/ gives the following:


ERROR: hostname: [Can't get realpath of the security file 
'/usr/local/etc/amanda/security.conf': No such file or directory]


Ekki


Am 07.06.2017 um 17:47 schrieb Jean-Louis Martineau:

The complete path to security.conf must be owned and writable only by
the root user

$ man amanda-security.conf

That's why it is by default in /etc and not in /etc/amanda which must be
writable by the amanda user.

Jean-Louis

On 07/06/17 11:37 AM, Ekkehard 'Ekki' Gehm wrote:
> Ahoi!
>
> I ran into an issue with the last update. Apparently amanda doesn't
> like my security.conf. And I do not know why. Any hints?
> The client is a FreeBSD Jail whilst the server is a FreeBSD Host...
>
>
> amcheck output:
>
> ERROR: hostname: [/s/var/db/amanda 
(/usr/local/etc/amanda/security.conf)

> is not owned by root]
>
> But:
> -rw-r--r-- 1 root wheel 2 Jun 7 17:12:55 2017 security.conf
>
> Version of amanda client: amanda-client-3.3.9,1
>
> Version of amanda server: amanda-server-3.3.6_5,1
>
> Thx in advance :-)
>
>
> Ekki
>


*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.





This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: security.conf and FreeBSD jails

[Ekkehard 'Ekki' Gehm]

Ahoi!

is there a config option to tell amanda where look for it? Because
moving the file to /etc/ gives the following:

ERROR: hostname: [Can't get realpath of the security file
'/usr/local/etc/amanda/security.conf': No such file or directory]

Ekki


Am 07.06.2017 um 17:47 schrieb Jean-Louis Martineau:
> The complete path to security.conf must be owned and writable only by
> the root user
>
> $ man amanda-security.conf
>
> That's why it is by default in /etc and not in /etc/amanda which must be
> writable by the amanda user.
>
> Jean-Louis
>
> On 07/06/17 11:37 AM, Ekkehard 'Ekki' Gehm wrote:
> > Ahoi!
> >
> > I ran into an issue with the last update. Apparently amanda doesn't
> > like my security.conf. And I do not know why. Any hints?
> > The client is a FreeBSD Jail whilst the server is a FreeBSD Host...
> >
> >
> > amcheck output:
> >
> > ERROR: hostname: [/s/var/db/amanda (/usr/local/etc/amanda/security.conf)
> > is not owned by root]
> >
> > But:
> > -rw-r--r-- 1 root wheel 2 Jun 7 17:12:55 2017 security.conf
> >
> > Version of amanda client: amanda-client-3.3.9,1
> >
> > Version of amanda server: amanda-server-3.3.6_5,1
> >
> > Thx in advance :-)
> >
> >
> > Ekki
> >
>
>
> *Disclaimer*
>
> This message is the property of *CARBONITE, INC.*
>  and may contain confidential or privileged
> information.
>
> If this message has been delivered to you by mistake, then do not copy
> or deliver this message to anyone. Instead, destroy it and notify me
> by reply e-mail.
>

Re: security.conf and FreeBSD jails

[Jean-Louis Martineau]

The complete path to security.conf must be owned and writable only by 
the root user


$ man amanda-security.conf

That's why it is by default in /etc and not in /etc/amanda which must be 
writable by the amanda user.


Jean-Louis

On 07/06/17 11:37 AM, Ekkehard 'Ekki' Gehm wrote:

Ahoi!

I ran into an issue with the last update. Apparently  amanda doesn't
like my security.conf. And I do not know why. Any hints?
The client is a FreeBSD Jail whilst the server is a FreeBSD Host...


amcheck output:

ERROR: hostname: [/s/var/db/amanda (/usr/local/etc/amanda/security.conf)
is not owned by root]

But:
-rw-r--r--   1 rootwheel 2 Jun  7 17:12:55 2017 security.conf

Version of amanda client: amanda-client-3.3.9,1

Version of amanda server: amanda-server-3.3.6_5,1

Thx in advance :-)


Ekki


This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

security.conf and FreeBSD jails

[Ekkehard 'Ekki' Gehm]

Ahoi!

I ran into an issue with the last update. Apparently  amanda doesn't
like my security.conf. And I do not know why. Any hints?
The client is a FreeBSD Jail whilst the server is a FreeBSD Host...


amcheck output:

ERROR: hostname: [/s/var/db/amanda (/usr/local/etc/amanda/security.conf)
is not owned by root]

But:
-rw-r--r--   1 rootwheel 2 Jun  7 17:12:55 2017 security.conf

Version of amanda client: amanda-client-3.3.9,1

Version of amanda server: amanda-server-3.3.6_5,1

Thx in advance :-)


Ekki