Hi Peter,
Thank you for your interest in systraq and reporting the issue. It's indeed
an annoying message.
From: Peter Wiersig <pe...@friesenpeter.de>, Date: Sun, 25 Feb 2018 13:06:42
+0100:
>
> during package installation the line
>
> ls: cannot access '/home/*/.ssh/a*': No such file or directory
>
> gets printed after package installation and my systems etckeeper
> run. My examination showed it initially from
> /etc/systraq/Makefile, after installing the version from buster
> the line comes from /usr/include/systraq/filetraq.mk
>
> I'm guessing the debian-systraq user isn't allowed to peek into my
> users home dirs due to filesystem permissions, but even if I
> change the one or two users directories now, future users adding
> the authorized_keys file in the future might get missed.
The culprit is indeed in usr/include/systraq/filetraq.mk , in
filetraq.main.conf:
echo '# $@: automatically generated' > $@
find /etc -not -readable -and -prune -or \( -perm -a+r -and -type f
-and -print \) | sort >> $@
ls -1 /home/*/.ssh/a* | sort >> $@
which is executed as user debian-systraq, e.g. during package upgrade via
/etc/apt/apt.conf.d/20systraq .
I'd like this code to give an error message if permissions are lacking, but
ideally _not_ when no files /home/*/.ssh/a* are present on the system. I
haven't managed to produce not too complicated code which does just that.
I'll spend some more brain cycles on it.
Anyway, as is commonly said: patches are welcome...
Bye,
Joost
