From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Alexander Strasser <eclipse7@gmx.net>
Subject: Re: [FFmpeg-devel] trac backups
Date: Wed, 13 Sep 2023 01:33:23 +0200
Message-ID: <20230912233323.GN8640@pb2> (raw)
In-Reply-To: <9881141C-00C4-4E03-927B-399426FE848B@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
On Wed, Sep 13, 2023 at 12:32:28AM +0200, Marvin Scholz wrote:
>
>
> On 13 Sep 2023, at 0:13, Michael Niedermayer wrote:
>
> > Hi all
> >
> > our trac backups died 6 months ago
> > i just noticed as i checked the backups before deleting spam with trac-admin
> > backups are working again
> >
> > failure reason where expired gpg keys
> >
> > thx
> >
> > PS: yeah, iam slightly unhappy noone noticed this for 6 months
>
> Who else other than you has access to the infrastructure?
all the root admins do
but that isnt the problem, even if 100 more people had access
the only way that was noticable it seems was if someone looked
either at the backups (which happily where generated with size 0 per file)
or the logs
ive added a gpg --recv-key so until the key server gets killed by the NSA
that might be avoided. Sadly gpg has no clean was to ignore key expiry
also ive pinged beastd (who wrote the trac backup scripts and is in CC)
and if he has no time, i guess ill have to look at why this was not more
vissible and how to fix that ...
But it seems theres no hurry
theres also the more radical solution of just making the backups public
as they are enrcypted anyway, it just doesnt feel like the first
choice. But it would avoid several issues like not noticing this or
other lost backups, ...
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If a bugfix only changes things apparently unrelated to the bug with no
further explanation, that is a good sign that the bugfix is wrong.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-09-12 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 22:13 Michael Niedermayer
2023-09-12 22:32 ` Marvin Scholz
2023-09-12 23:33 ` Michael Niedermayer [this message]
2023-09-13 9:05 ` Jean-Baptiste Kempf
2023-09-13 9:52 ` Paul B Mahol
2023-09-13 16:38 ` Michael Niedermayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230912233323.GN8640@pb2 \
--to=michael@niedermayer.cc \
--cc=eclipse7@gmx.net \
--cc=ffmpeg-devel@ffmpeg.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git