diff --git a/.gnupg/.#lk0x0000556501610fb0.miraculix.6734 b/.gnupg/.#lk0x0000556501610fb0.miraculix.6734 deleted file mode 100644 index e06c8c0..0000000 --- a/.gnupg/.#lk0x0000556501610fb0.miraculix.6734 +++ /dev/null @@ -1,2 +0,0 @@ - 6734 -miraculix diff --git a/.gnupg/.#lk0x00005568f84e9080.miraculix.41248 b/.gnupg/.#lk0x00005568f84e9080.miraculix.41248 deleted file mode 100644 index ef47b04..0000000 --- a/.gnupg/.#lk0x00005568f84e9080.miraculix.41248 +++ /dev/null @@ -1,2 +0,0 @@ - 41248 -miraculix diff --git a/.gnupg/.#lk0x000055d038c48fb0.miraculix.6707 b/.gnupg/.#lk0x000055d038c48fb0.miraculix.6707 deleted file mode 100644 index ea65218..0000000 --- a/.gnupg/.#lk0x000055d038c48fb0.miraculix.6707 +++ /dev/null @@ -1,2 +0,0 @@ - 6707 -miraculix diff --git a/.gnupg/.#lk0x00005632791d9080.miraculix.456739 b/.gnupg/.#lk0x00005632791d9080.miraculix.456739 deleted file mode 100644 index 7e65f06..0000000 --- a/.gnupg/.#lk0x00005632791d9080.miraculix.456739 +++ /dev/null @@ -1,2 +0,0 @@ - 456739 -miraculix diff --git a/.gnupg/.#lk0x00005638836af090.miraculix.19367 b/.gnupg/.#lk0x00005638836af090.miraculix.19367 deleted file mode 100644 index 3000160..0000000 --- a/.gnupg/.#lk0x00005638836af090.miraculix.19367 +++ /dev/null @@ -1,2 +0,0 @@ - 19367 -miraculix diff --git a/.gnupg/.gpg-v21-migrated b/.gnupg/.gpg-v21-migrated deleted file mode 100644 index e69de29..0000000 diff --git a/.gnupg/crls.d/DIR.txt b/.gnupg/crls.d/DIR.txt deleted file mode 100644 index 712b8ad..0000000 --- a/.gnupg/crls.d/DIR.txt +++ /dev/null @@ -1,6 +0,0 @@ -v:1: -u:A4AC4139F7C341B7AB4F421A7DE819A891E8E631:CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3:http%3A//crl.globalsign.com/root-r3.crl:20210224T000000:20210715T000000:A4AD061263D18F16C066BF7B0E5115E0:2D:::D69B561148F01C77C54578C10926DF5B856976AD -u:C72A5C51E00B29161DB11B29D9350DE1FAB48CE5:CN=Trusted Root CA SHA256 G2,O=GlobalSign nv-sa,OU=Trusted Root,C=BE:http%3A//crl.globalsign.com/trustrootsha2g2.crl:20200318T000000:20200715T000000:B33766B3A5D352D1FE7DFF32595D3259:21:::D69B561148F01C77C54578C10926DF5B856976AD -u:CF21490F95A26145AD0898FFA51095BBD8715809:CN=DPDHL User CA I3,O=Deutsche Post,L=Bonn,ST=Nordrhein-Westfalen,C=DE:http%3A//keyserver.dhl.com/pki/i3/dpdhl_user_i3.crl:20200615T205507:20200619T211507:165527980997AB65DBD8ED3F7ECDAE41:02AB2F:::D69B561148F01C77C54578C10926DF5B856976AD -u:DFDC46957947D4664D2DCF76B30925F37BA4FEA2:CN=DPDHL User CA I4,O=Deutsche Post AG,C=DE:http%3A//crl.globalsign.com/ca/dhlusercai4.crl:20200826T150049:20200902T150049:998DC93BD836341DF585E1A1EA664AE3:5F467921:::D69B561148F01C77C54578C10926DF5B856976AD -u:44A42A49CB0ACF82612D0E298271CEE5EAFB160F:CN=DPDHL User CA I5,O=Deutsche Post AG,C=DE:http%3A//crl.globalsign.com/ca/dhlusercai5.crl:20210515T162026:20210522T162026:F97EB4966F139F778AD3A2B074FC7760:609FF4CA:::D69B561148F01C77C54578C10926DF5B856976AD diff --git a/.gnupg/crls.d/crl-44A42A49CB0ACF82612D0E298271CEE5EAFB160F.db b/.gnupg/crls.d/crl-44A42A49CB0ACF82612D0E298271CEE5EAFB160F.db deleted file mode 100644 index 3c36bfd..0000000 Binary files a/.gnupg/crls.d/crl-44A42A49CB0ACF82612D0E298271CEE5EAFB160F.db and /dev/null differ diff --git a/.gnupg/crls.d/crl-A4AC4139F7C341B7AB4F421A7DE819A891E8E631.db b/.gnupg/crls.d/crl-A4AC4139F7C341B7AB4F421A7DE819A891E8E631.db deleted file mode 100644 index a91af11..0000000 Binary files a/.gnupg/crls.d/crl-A4AC4139F7C341B7AB4F421A7DE819A891E8E631.db and /dev/null differ diff --git a/.gnupg/crls.d/crl-C72A5C51E00B29161DB11B29D9350DE1FAB48CE5.db b/.gnupg/crls.d/crl-C72A5C51E00B29161DB11B29D9350DE1FAB48CE5.db deleted file mode 100644 index 2ff098a..0000000 Binary files a/.gnupg/crls.d/crl-C72A5C51E00B29161DB11B29D9350DE1FAB48CE5.db and /dev/null differ diff --git a/.gnupg/crls.d/crl-CF21490F95A26145AD0898FFA51095BBD8715809.db b/.gnupg/crls.d/crl-CF21490F95A26145AD0898FFA51095BBD8715809.db deleted file mode 100644 index 5e96d93..0000000 Binary files a/.gnupg/crls.d/crl-CF21490F95A26145AD0898FFA51095BBD8715809.db and /dev/null differ diff --git a/.gnupg/crls.d/crl-DFDC46957947D4664D2DCF76B30925F37BA4FEA2.db b/.gnupg/crls.d/crl-DFDC46957947D4664D2DCF76B30925F37BA4FEA2.db deleted file mode 100644 index 793a652..0000000 Binary files a/.gnupg/crls.d/crl-DFDC46957947D4664D2DCF76B30925F37BA4FEA2.db and /dev/null differ diff --git a/.gnupg/gpg-agent.conf b/.gnupg/gpg-agent.conf deleted file mode 100644 index 7f942b1..0000000 --- a/.gnupg/gpg-agent.conf +++ /dev/null @@ -1,18 +0,0 @@ -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.4.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.3.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.0.pep.bkp' - -default-cache-ttl 300 -max-cache-ttl 999999 -pinentry-program /usr/bin/pinentry diff --git a/.gnupg/gpg-agent.conf.0.pep.bkp b/.gnupg/gpg-agent.conf.0.pep.bkp deleted file mode 100644 index 866774f..0000000 --- a/.gnupg/gpg-agent.conf.0.pep.bkp +++ /dev/null @@ -1,5 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -default-cache-ttl 300 -max-cache-ttl 999999 diff --git a/.gnupg/gpg-agent.conf.1.pep.bkp b/.gnupg/gpg-agent.conf.1.pep.bkp deleted file mode 100644 index be8dabd..0000000 --- a/.gnupg/gpg-agent.conf.1.pep.bkp +++ /dev/null @@ -1,8 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.0.pep.bkp' - -default-cache-ttl 300 -max-cache-ttl 999999 diff --git a/.gnupg/gpg-agent.conf.2.pep.bkp b/.gnupg/gpg-agent.conf.2.pep.bkp deleted file mode 100644 index b5e7c93..0000000 --- a/.gnupg/gpg-agent.conf.2.pep.bkp +++ /dev/null @@ -1,12 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.0.pep.bkp' - -default-cache-ttl 300 -max-cache-ttl 999999 -pinentry-program /usr/bin/pinentry diff --git a/.gnupg/gpg-agent.conf.3.pep.bkp b/.gnupg/gpg-agent.conf.3.pep.bkp deleted file mode 100644 index 53f516e..0000000 --- a/.gnupg/gpg-agent.conf.3.pep.bkp +++ /dev/null @@ -1,15 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.0.pep.bkp' - -default-cache-ttl 300 -max-cache-ttl 999999 -pinentry-program /usr/bin/pinentry diff --git a/.gnupg/gpg-agent.conf.4.pep.bkp b/.gnupg/gpg-agent.conf.4.pep.bkp deleted file mode 100644 index 04edbe0..0000000 --- a/.gnupg/gpg-agent.conf.4.pep.bkp +++ /dev/null @@ -1,18 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.3.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg-agent.conf.0.pep.bkp' - -default-cache-ttl 300 -max-cache-ttl 999999 -pinentry-program /usr/bin/pinentry diff --git a/.gnupg/gpg.conf b/.gnupg/gpg.conf deleted file mode 100644 index 9eab735..0000000 --- a/.gnupg/gpg.conf +++ /dev/null @@ -1,218 +0,0 @@ -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.4.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.3.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.0.pep.bkp' - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - -cert-digest-algo SHA256 -no-emit-version -no-comments -personal-cipher-preferences AES AES256 AES192 CAST5 -personal-digest-preferences SHA256 SHA512 SHA384 SHA224 -ignore-time-conflict -allow-freeform-uid diff --git a/.gnupg/gpg.conf.0.pep.bkp b/.gnupg/gpg.conf.0.pep.bkp deleted file mode 100644 index 9e20e0e..0000000 --- a/.gnupg/gpg.conf.0.pep.bkp +++ /dev/null @@ -1,199 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - diff --git a/.gnupg/gpg.conf.1.pep.bkp b/.gnupg/gpg.conf.1.pep.bkp deleted file mode 100644 index 58d182e..0000000 --- a/.gnupg/gpg.conf.1.pep.bkp +++ /dev/null @@ -1,209 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.0.pep.bkp' - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - -cert-digest-algo SHA256 -no-emit-version -no-comments -personal-cipher-preferences AES AES256 AES192 CAST5 -personal-digest-preferences SHA256 SHA512 SHA384 SHA224 -ignore-time-conflict -allow-freeform-uid diff --git a/.gnupg/gpg.conf.2.pep.bkp b/.gnupg/gpg.conf.2.pep.bkp deleted file mode 100644 index 18a9ee8..0000000 --- a/.gnupg/gpg.conf.2.pep.bkp +++ /dev/null @@ -1,212 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.0.pep.bkp' - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - -cert-digest-algo SHA256 -no-emit-version -no-comments -personal-cipher-preferences AES AES256 AES192 CAST5 -personal-digest-preferences SHA256 SHA512 SHA384 SHA224 -ignore-time-conflict -allow-freeform-uid diff --git a/.gnupg/gpg.conf.3.pep.bkp b/.gnupg/gpg.conf.3.pep.bkp deleted file mode 100644 index bc4001e..0000000 --- a/.gnupg/gpg.conf.3.pep.bkp +++ /dev/null @@ -1,215 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.0.pep.bkp' - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - -cert-digest-algo SHA256 -no-emit-version -no-comments -personal-cipher-preferences AES AES256 AES192 CAST5 -personal-digest-preferences SHA256 SHA512 SHA384 SHA224 -ignore-time-conflict -allow-freeform-uid diff --git a/.gnupg/gpg.conf.4.pep.bkp b/.gnupg/gpg.conf.4.pep.bkp deleted file mode 100644 index 6015258..0000000 --- a/.gnupg/gpg.conf.4.pep.bkp +++ /dev/null @@ -1,218 +0,0 @@ -# Backup created by pEp. -# If GnuPG and pEp work smoothly this file may safely be removed. - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.3.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.2.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.1.pep.bkp' - -# File re-created by pEp -# See backup in '/home/user/flo/.gnupg/gpg.conf.0.pep.bkp' - -# Options for GnuPG -# Copyright 1998, 1999, 2000, 2001, 2002, 2003, -# 2010 Free Software Foundation, Inc. -# -# This file is free software; as a special exception the author gives -# unlimited permission to copy and/or distribute it, with or without -# modifications, as long as this notice is preserved. -# -# This file is distributed in the hope that it will be useful, but -# WITHOUT ANY WARRANTY, to the extent permitted by law; without even the -# implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. -# -# Unless you specify which option file to use (with the command line -# option "--options filename"), GnuPG uses the file ~/.gnupg/gpg.conf -# by default. -# -# An options file can contain any long options which are available in -# GnuPG. If the first non white space character of a line is a '#', -# this line is ignored. Empty lines are also ignored. -# -# See the man page for a list of options. - -# Uncomment the following option to get rid of the copyright notice - -#no-greeting - -# If you have more than 1 secret key in your keyring, you may want to -# uncomment the following option and set your preferred keyid. - -#default-key 621CC013 - -# If you do not pass a recipient to gpg, it will ask for one. Using -# this option you can encrypt to a default key. Key validation will -# not be done in this case. The second form uses the default key as -# default recipient. - -#default-recipient some-user-id -#default-recipient-self - -# By default GnuPG creates version 4 signatures for data files as -# specified by OpenPGP. Some earlier (PGP 6, PGP 7) versions of PGP -# require the older version 3 signatures. Setting this option forces -# GnuPG to create version 3 signatures. - -#force-v3-sigs - -# Because some mailers change lines starting with "From " to ">From " -# it is good to handle such lines in a special way when creating -# cleartext signatures; all other PGP versions do it this way too. -# To enable full OpenPGP compliance you may want to use this option. - -#no-escape-from-lines - -# When verifying a signature made from a subkey, ensure that the cross -# certification "back signature" on the subkey is present and valid. -# This protects against a subtle attack against subkeys that can sign. -# Defaults to --no-require-cross-certification. However for new -# installations it should be enabled. - -require-cross-certification - - -# If you do not use the Latin-1 (ISO-8859-1) charset, you should tell -# GnuPG which is the native character set. Please check the man page -# for supported character sets. This character set is only used for -# metadata and not for the actual message which does not undergo any -# translation. Note that future version of GnuPG will change to UTF-8 -# as default character set. - -#charset utf-8 - -# Group names may be defined like this: -# group mynames = paige 0x12345678 joe patti -# -# Any time "mynames" is a recipient (-r or --recipient), it will be -# expanded to the names "paige", "joe", and "patti", and the key ID -# "0x12345678". Note there is only one level of expansion - you -# cannot make an group that points to another group. Note also that -# if there are spaces in the recipient name, this will appear as two -# recipients. In these cases it is better to use the key ID. - -#group mynames = paige 0x12345678 joe patti - -# Some old Windows platforms require 8.3 filenames. If your system -# can handle long filenames, uncomment this. - -#no-mangle-dos-filenames - -# Lock the file only once for the lifetime of a process. If you do -# not define this, the lock will be obtained and released every time -# it is needed - normally this is not needed. - -#lock-once - -# GnuPG can send and receive keys to and from a keyserver. These -# servers can be HKP, email, or LDAP (if GnuPG is built with LDAP -# support). -# -# Example HKP keyservers: -# hkp://keys.gnupg.net -# -# Example LDAP keyservers: -# ldap://pgp.surfnet.nl:11370 -# -# Regular URL syntax applies, and you can set an alternate port -# through the usual method: -# hkp://keyserver.example.net:22742 -# -# If you have problems connecting to a HKP server through a buggy http -# proxy, you can use keyserver option broken-http-proxy (see below), -# but first you should make sure that you have read the man page -# regarding proxies (keyserver option honor-http-proxy) -# -# Most users just set the name and type of their preferred keyserver. -# Note that most servers (with the notable exception of -# ldap://keyserver.pgp.com) synchronize changes with each other. Note -# also that a single server name may actually point to multiple -# servers via DNS round-robin. hkp://keys.gnupg.net is an example of -# such a "server", which spreads the load over a number of physical -# servers. To see the IP address of the server actually used, you may use -# the "--keyserver-options debug". - -keyserver hkp://keys.gnupg.net -#keyserver http://http-keys.gnupg.net -#keyserver mailto:pgp-public-keys@keys.nl.pgp.net - -# Common options for keyserver functions: -# -# include-disabled = when searching, include keys marked as "disabled" -# on the keyserver (not all keyservers support this). -# -# no-include-revoked = when searching, do not include keys marked as -# "revoked" on the keyserver. -# -# verbose = show more information as the keys are fetched. -# Can be used more than once to increase the amount -# of information shown. -# -# use-temp-files = use temporary files instead of a pipe to talk to the -# keyserver. Some platforms (Win32 for one) always -# have this on. -# -# keep-temp-files = do not delete temporary files after using them -# (really only useful for debugging) -# -# honor-http-proxy = if the keyserver uses HTTP, honor the http_proxy -# environment variable -# -# broken-http-proxy = try to work around a buggy HTTP proxy -# -# auto-key-retrieve = automatically fetch keys as needed from the keyserver -# when verifying signatures or when importing keys that -# have been revoked by a revocation key that is not -# present on the keyring. -# -# no-include-attributes = do not include attribute IDs (aka "photo IDs") -# when sending keys to the keyserver. - -#keyserver-options auto-key-retrieve - -# Uncomment this line to display photo user IDs in key listings and -# when a signature from a key with a photo is verified. - -#show-photos - -# Use this program to display photo user IDs -# -# %i is expanded to a temporary file that contains the photo. -# %I is the same as %i, but the file isn't deleted afterwards by GnuPG. -# %k is expanded to the key ID of the key. -# %K is expanded to the long OpenPGP key ID of the key. -# %t is expanded to the extension of the image (e.g. "jpg"). -# %T is expanded to the MIME type of the image (e.g. "image/jpeg"). -# %f is expanded to the fingerprint of the key. -# %% is %, of course. -# -# If %i or %I are not present, then the photo is supplied to the -# viewer on standard input. If your platform supports it, standard -# input is the best way to do this as it avoids the time and effort in -# generating and then cleaning up a secure temp file. -# -# The default program is "xloadimage -fork -quiet -title 'KeyID 0x%k' stdin" -# On Mac OS X and Windows, the default is to use your regular JPEG image -# viewer. -# -# Some other viewers: -# photo-viewer "qiv %i" -# photo-viewer "ee %i" -# photo-viewer "display -title 'KeyID 0x%k'" -# -# This one saves a copy of the photo ID in your home directory: -# photo-viewer "cat > ~/photoid-for-key-%k.%t" -# -# Use your MIME handler to view photos: -# photo-viewer "metamail -q -d -b -c %T -s 'KeyID 0x%k' -f GnuPG" - -cert-digest-algo SHA256 -no-emit-version -no-comments -personal-cipher-preferences AES AES256 AES192 CAST5 -personal-digest-preferences SHA256 SHA512 SHA384 SHA224 -ignore-time-conflict -allow-freeform-uid diff --git a/.gnupg/private-keys-v1.d/0B2FDB300499EDDAFBFBCD45B97B4518244B09CA.key b/.gnupg/private-keys-v1.d/0B2FDB300499EDDAFBFBCD45B97B4518244B09CA.key deleted file mode 100644 index d5a70e4..0000000 Binary files a/.gnupg/private-keys-v1.d/0B2FDB300499EDDAFBFBCD45B97B4518244B09CA.key and /dev/null differ diff --git a/.gnupg/private-keys-v1.d/66509F585B8B2B3E549150E3EA965C60F06A7AA5.key b/.gnupg/private-keys-v1.d/66509F585B8B2B3E549150E3EA965C60F06A7AA5.key deleted file mode 100644 index be5b502..0000000 --- a/.gnupg/private-keys-v1.d/66509F585B8B2B3E549150E3EA965C60F06A7AA5.key +++ /dev/null @@ -1,10 +0,0 @@ -Key: (shadowed-private-key (rsa (n #00CF719485F94F85FCEABD9B8D7B526CD5E - 1FD61869B16CF9D1217048D6C15C0B529FCD2CE9366819E91924329F0CAB7A4E9C2468 - 4F5825FACA8536DC638EA293BFA9F384C54EF3DD965E8E10CA9718DA41B96E8CFFE924 - 3528F3426901CEEE87EAC6FA315B14F2750A949BFE74969E186E25109AE52002AAA72E - 1A0C5CF4D494BE643FD0138ED2F0CBE7834CB16DC1B6CFE7750E414F28B80641978E0A - C044387C47074A07DCE5C2B8CD69ACE1FEBB4BF2AFB7D8081F17C2D6DAB89A440EB4C1 - 5F1E722B7AEE234637E27260FA6B9AD0062418691D5128A21DF9A439814E7A12C1CECA - 7B3C4951CC2ECA16D43B00AB169128CCFDFBE3C49F6DFF1EAB7B1689059#)(e - #010001#)(shadowed t1-v1 (#D2760001240102000006045472820000# - OPENPGP.2)))) diff --git a/.gnupg/private-keys-v1.d/7D14A034B398A85E96078FBFAABD210DEFCFD245.key b/.gnupg/private-keys-v1.d/7D14A034B398A85E96078FBFAABD210DEFCFD245.key deleted file mode 100644 index 6df6915..0000000 Binary files a/.gnupg/private-keys-v1.d/7D14A034B398A85E96078FBFAABD210DEFCFD245.key and /dev/null differ diff --git a/.gnupg/private-keys-v1.d/9D064FDB4779225CBC26031105478D991F37E048.key b/.gnupg/private-keys-v1.d/9D064FDB4779225CBC26031105478D991F37E048.key deleted file mode 100644 index 58670e2..0000000 --- a/.gnupg/private-keys-v1.d/9D064FDB4779225CBC26031105478D991F37E048.key +++ /dev/null @@ -1,10 +0,0 @@ -Key: (shadowed-private-key (rsa (n #00B226D35FB56B9888BB1BFE2BBEBD3CB39 - 9E9A3395F87A93F3DDBF0196EAC19D725728740829253E47FFF7975BEE0C52D1F70ED3 - E823D09A0D87DDEFF43469CAE8C8B15F6F6F7BB25164B0835511B05EE3EABFFD795A36 - 5B78F7E34153BD3BA06B6E11C297E8FB83DD244A101B25A9DF8D347A1E124030578A62 - 81AC86D16029B4C91C5C573D32C8BA4C2E9C170F40F7AB7D67CDEDA476D44042B07CF9 - D9A76503F8EFC71AEDBBDA6DACCDD65D1849F7085154AC75C846DC2F5AFAB2C0C5A052 - 87B7A67CB3E25C306E3563C92DE775EA966DF7482B6A4097A33E2818D3D330742BE0DD - F9C53E9845B0F17FEB94FF3CF0520B019C922692D013B5DB0CF98FF395F#)(e - #010001#)(shadowed t1-v1 (#D2760001240102000006045472820000# - OPENPGP.1)))) diff --git a/.gnupg/private-keys-v1.d/A1115922B14E052413ACA3291C90DAD6E46612EE.key b/.gnupg/private-keys-v1.d/A1115922B14E052413ACA3291C90DAD6E46612EE.key deleted file mode 100644 index 6656fb3..0000000 --- a/.gnupg/private-keys-v1.d/A1115922B14E052413ACA3291C90DAD6E46612EE.key +++ /dev/null @@ -1,10 +0,0 @@ -Key: (shadowed-private-key (rsa (n #00A8ECD2EC3479E9B2864F637F97BA64DF0 - F769B2D394950F7CD8A1387F704836F8312A686D7A44219E41CA0CDDE874FF8FE923A1 - 8A0580904F74F5FF988640FA5EA2E666037555DBDCE3E3673DF2C84F729518E89F8EC4 - 0792314AE4B923245BBC239E2450A86185CC84509358CCD95AE78383490DE1150AE232 - 2CCA4B86F431C6A89B045AFF4AA51DAB30DB0B5242F96E7C8273CD1B94D240943E63C2 - 323426C6A78B6430747F8599EB76A663DFA3748C62107696E31727C7750A1742D93214 - D7E18FD570BCB086208F193684E7B6F587E25A29FBD3E7A9D03BD83066BED4A08208A3 - DF74C9E3D874BC651BCDAE2644CD8EFEFE3780B8C32EA7477BBF8FFC2DD#)(e - #010001#)(shadowed t1-v1 (#D2760001240102000006045472820000# - OPENPGP.3)))) diff --git a/.gnupg/private-keys-v1.d/DC84B280E55050A370900517AF00FCE15562A412.key b/.gnupg/private-keys-v1.d/DC84B280E55050A370900517AF00FCE15562A412.key deleted file mode 100644 index 8c55375..0000000 Binary files a/.gnupg/private-keys-v1.d/DC84B280E55050A370900517AF00FCE15562A412.key and /dev/null differ diff --git a/.gnupg/pubring.gpg b/.gnupg/pubring.gpg deleted file mode 100644 index d8fc795..0000000 Binary files a/.gnupg/pubring.gpg and /dev/null differ diff --git a/.gnupg/pubring.gpg~ b/.gnupg/pubring.gpg~ deleted file mode 100644 index 0996035..0000000 Binary files a/.gnupg/pubring.gpg~ and /dev/null differ diff --git a/.gnupg/pubring.kbx b/.gnupg/pubring.kbx deleted file mode 100644 index f0843ed..0000000 Binary files a/.gnupg/pubring.kbx and /dev/null differ diff --git a/.gnupg/pubring.kbx~ b/.gnupg/pubring.kbx~ deleted file mode 100644 index 5410492..0000000 Binary files a/.gnupg/pubring.kbx~ and /dev/null differ diff --git a/.gnupg/random_seed b/.gnupg/random_seed deleted file mode 100644 index 51a45c8..0000000 Binary files a/.gnupg/random_seed and /dev/null differ diff --git a/.gnupg/reader_0.status b/.gnupg/reader_0.status deleted file mode 100644 index 6a6e304..0000000 --- a/.gnupg/reader_0.status +++ /dev/null @@ -1 +0,0 @@ -NOCARD diff --git a/.gnupg/secring.gpg b/.gnupg/secring.gpg deleted file mode 100644 index 12d83d3..0000000 Binary files a/.gnupg/secring.gpg and /dev/null differ diff --git a/.gnupg/tofu.db b/.gnupg/tofu.db deleted file mode 100644 index 4a8a3c0..0000000 Binary files a/.gnupg/tofu.db and /dev/null differ diff --git a/.gnupg/trustdb.gpg b/.gnupg/trustdb.gpg deleted file mode 100644 index f3f0120..0000000 Binary files a/.gnupg/trustdb.gpg and /dev/null differ diff --git a/.gnupg/trustlist.txt b/.gnupg/trustlist.txt deleted file mode 100644 index 0815974..0000000 --- a/.gnupg/trustlist.txt +++ /dev/null @@ -1,19 +0,0 @@ -# This is the list of trusted keys. Comment lines, like this one, as -# well as empty lines are ignored. Lines have a length limit but this -# is not a serious limitation as the format of the entries is fixed and -# checked by gpg-agent. A non-comment line starts with optional white -# space, followed by the SHA-1 fingerpint in hex, followed by a flag -# which may be one of 'P', 'S' or '*' and optionally followed by a list of -# other flags. The fingerprint may be prefixed with a '!' to mark the -# key as not trusted. You should give the gpg-agent a HUP or run the -# command "gpgconf --reload gpg-agent" after changing this file. - - -# Include the default trust list -include-default - - -# CN=GlobalSign -# OU=GlobalSign Root CA - R3 -# O=GlobalSign -D6:9B:56:11:48:F0:1C:77:C5:45:78:C1:09:26:DF:5B:85:69:76:AD S relax