Maurizio Caloro:
>
> On 27.06.2022 00:24, Wietse Venema wrote:
> > Maurizio Caloro:
> >
> > setup also opendkim and will appear now the error "
> >> *key data is not secure: / is writeable and owned by uid 110 which is
> >> not the executing uid (115)* *or the superuser*"
> >> it's seem that i
On Mon, Jun 27, 2022 at 07:19:59AM +0200, Maurizio Caloro
wrote:
> On 27.06.2022 00:24, Wietse Venema wrote:
> > Maurizio Caloro:
> >
> > setup also opendkim and will appear now the error "
> > > *key data is not secure: / is writeable and owned by uid 110 which
> > > is not the executing uid
On Mon, Jun 27, 2022 at 12:00:20AM +0200, Maurizio Caloro
wrote:
>
> setup also opendkim and will appear now the error "key data is not secure: /
> is writeable and owned by uid 110 which is not the executing uid (115)"
> it's seem that i have permission issue?
>
> # opendkim -V
>
On 27.06.22 00:00, Maurizio Caloro wrote:
setup also opendkim and will appear now the error "key data is not
secure: / is writeable and owned by uid 110 which is not the executing
uid (115)"
this looks like you have set owner of root directory to non-root user
it's seem that i have
On 27.06.2022 00:24, Wietse Venema wrote:
Maurizio Caloro:
setup also opendkim and will appear now the error "
*key data is not secure: / is writeable and owned by uid 110 which is
not the executing uid (115)* *or the superuser*"
it's seem that i have permission issue?
Look at the output
Maurizio Caloro:
>
> setup also opendkim and will appear now the error "key data is not
> secure: / is writeable and owned by uid 110 which is not the executing
> uid (115)"
> it's seem that i have permission issue?
Look at the output from:
ls -ld /
Wietse
setup also opendkim and will appear now the error "key data is not
secure: / is writeable and owned by uid 110 which is not the executing
uid (115)"
it's seem that i have permission issue?
# opendkim -V
opendkim: OpenDKIM Filter v2.11.0
Compiled with OpenSSL 1.1.1n 15 Mar 2022
