On 2019-02-15 09:10, Juergen Harms wrote:
> On 15.02.19 04:41, backu...@kosowsky.org wrote:
>
>> ...
>>> I was surprised to find that popular distros like Ubuntu and Debian do
>>> not support v4 even though the presumably stable v4.0 was released
>>> almost 2 years ago.
>>> Any ideas why the distros haven't moved to v4?
>> ...
>
> Mageia
> ------
> Mageia, both in its stable (6.1) and its development (cauldron) versions, is
> still offering v3. This is due to a problem with directories in cpool/ being
> created by v4 with world writeable permissions (probably also in pc/, I can't
> verify at present), see https://bugs.mageia.org/show_bug.cgi?id=24010
>
> Since the parent BackupPC directory on the server should have 0 world access
> permissions this is not dramatic. But there is also the issue that v4 makes
> msec (Mageia security checking tool) output tons of security warnings about
> world-writeable directories - and it is bad security policy to accumulate
> backup data that has the flaw of non-perfect write protection.
>
> With the suggested patch, directory permissions do become OK and v4.0 runs
> smoothtly - but the patch is only a temporary workaround (made with the
> intent to exlude the risk of introducing problems elsewhere). The underlying
> problem is probably a umask issue.
>
> * I'm surprised at this as BackupPC has a UMaskMode configuration parameter
> which defaults to 027. Are you saying the setting is being ignored?
>
> Personally, after applying the patch, I am perfectly happy with v4 and use a
> self-made correspondingly built package in production: full satisfaction.
> Presently my server is configured to maintain the old v3 data along with the
> newly added v4 backup data. I have not yet decided whether I will convert my
> backup data to all-v4.
>
> Mageia is presently preparing a new stable release (Mageia-7, release
> foreseen for something like April). The decision lies with the development
> engineers whether they consider the patch sufficient for having v4 in
> Mageia-7 or whether they expect a well thought-out correction from upstream.
>
> _______________________________________________
> BackupPC-users mailing list
> BackupPC-users@lists.sourceforge.net
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
