Matthias Apitz wrote: > The page about how to configure mutt with oauth2 support says: > > https://www.vanormondt.net/~peter/blog/2021-03-16-mutt-office365-mfa.html > ... > > Edit the python script and insert your GPG identity in the > "ENCRYPTION_PIPE" construct. > Add client id ('08162f7c-0fd2-4200-a84a-f25a4db0b584') and client_secret > ('TxRBilcHdC6WGBee]fs?QR:SJ8nI[g82'), as per these instructions, to the > "microsoft" registrations. > > My gpg ID is DC4AA850 from the command below: > > $ gpg --keyid-format short --fingerprint guru > pub rsa4096/DC4AA850 2024-05-12 [SC] > Key fingerprint = 895A 3082 6A0A 0269 0D38 5529 B84C 65D9 DC4A A850 > uid [ultimate] Matthias Apitz (OpenPGP card 2) <g...@unixarea.de> > sub rsa4096/237B4D65 2024-05-12 [A] > sub rsa4096/981CBAF1 2024-05-12 [E] > > Should this be entered as 'DC4AA850' or as '0xDC4AA850' in the script > mutt_oauth2.py
It's just passed to gpg, so any of the ways you can specify
an identity to gpg will work.
The code looks like this:
ENCRYPTION_PIPE = ['gpg', '--encrypt', '--recipient', 'YOUR_GPG_IDENTITY']
I use a fingerprint for things like this. (Modern gpg
reports the fingerprint as a long string without any extra
options and short keyid's are essentially worthless, IMO.)
The "HOW TO SPECIFY A USER ID" section of gpg(1) details the
numerous methods available to you.
--
Todd
signature.asc
Description: PGP signature
