Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] doc/git-howto.texi: Document commit signing
Date: Tue, 23 Aug 2022 20:00:32 +0200
Message-ID: <20220823180032.GM2088045@pb2> (raw)
In-Reply-To: <20220809221902.GC2088045@pb2>


[-- Attachment #1.1: Type: text/plain, Size: 2120 bytes --]

On Wed, Aug 10, 2022 at 12:19:02AM +0200, Michael Niedermayer wrote:
> On Tue, Aug 09, 2022 at 04:38:56PM -0300, James Almer wrote:
> > On 8/9/2022 4:34 PM, Michael Niedermayer wrote:
> > > From: Michael Niedermayer <michael-git@niedermayer.cc>
[...]
> 
> > 
> > > +github consider mismatches a reason to declare such commits unverified. After generating a key you
> > > +can add it to the MAINTAINER file and upload it to a keyserver.
> > 
> > Maybe link some external documentation about gpg keys, explaining the
> > difference between public and private keys, 
> 
> what do you recommend ?

ping ?
we could link to the gpg docs but that seems kind of silly


> 
> 
> > how to encrypt the private one
> > with a passphrase, etc.
> 
> Have you tried to generate a gpg key without a passphrase ?
> I just tried, and failed, gpg keeps asking for a passphrase until you enter
> one or kill it. It kept haunting me and asking for a passphrase even after
> trying ctrl-c 
> 
> 
> > Sites like gitlab tell you to not attempt to upload private keys, 
> 
> ok
> 
> 
> > so i
> > imagine quite a lot of people have mistakenly done so in the past.
> 
> imagine?
> 
> but what do you suggest? we can document how someone can create a key
> upload it and so on. You can provide me with a url that describes a
> working documentation for that, i surely do not have one. alot of
> documentations are somewhat bad. Many keyservers have died recently
> some existing keys like DSA seem to have some affinity to SHA1, and
> SHA1 is rejected today while at the same time still default on many
> setups, the one documentation i saw today to fix that DSA/SHA1 issue
> requires you to have a backup as it breaks your keys and is wrong.




[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Dictatorship: All citizens are under surveillance, all their steps and
actions recorded, for the politicians to enforce control.
Democracy: All politicians are under surveillance, all their steps and
actions recorded, for the citizens to enforce control.

[-- 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".

  reply	other threads:[~2022-08-23 18:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 19:34 Michael Niedermayer
2022-08-09 19:38 ` James Almer
2022-08-09 22:19   ` Michael Niedermayer
2022-08-23 18:00     ` Michael Niedermayer [this message]
2022-08-23 18:07       ` James Almer
2022-08-28 17:50         ` 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=20220823180032.GM2088045@pb2 \
    --to=michael@niedermayer.cc \
    --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