Is there any way to determine the encoding for a user ID string?
At first blush it appears the answer is "no, but most people use UTF-8."
If so that's fine, but I'll have to silently discard a number of user
IDs that appear to be in foreign encodings or are garbled UTF-8. I'd
prefer not to do th
I am getting this error when running the command make. I would appreciate any
help I could get.
../../g10/gpg2 --homedir . --quiet --yes --no-permission-warning --import
./pubdemo.asc
ld.so.1: gpg2: fatal: relocation error: file /usr/lib/libgcrypt.so.20: symbol
gpgrt_lock_lock: referenced sym
> On 23 May 2016, at 20:19, Robert J. Hansen wrote:
>
> Is there any way to determine the encoding for a user ID string?
>
> At first blush it appears the answer is "no, but most people use UTF-8."
You can tell fairly reliably if someone is using either vanilla ascii or UTF8,
in the cases of
Dear All,
I have a long use key that has been created back in 2002 using
- I think - some gpg 1.0.x version.
This key, at least when exported with "gpg2 --export" (or
"--export-secret-key"), seems to be in some "key packet version 2"
format, as "gpg2 --export | gpg2 --list-packets" shows:
On 05/23/2016 09:56 PM, Bjoern Kahl wrote:
> I'd like to convert the existing secret key and the corresponding
> public key, preferably without destroying the signatures, from
> "version 2" to "version 4".
This is not possible.
--
Kristian Fiskerstrand
Blog: http
> In the case of "all 8-bit characters, no 7-bit" you're dealing with
> either a practical joker or EBCDIC. Same thing really...
Or KOI-8R/Windows-1251.
> After that you're into heuristics. There are quite a few programs out
> there that attempt to detect encodings statistically, but with such a
On 23 May 2016, at 23:24, Robert J. Hansen wrote:
>> In the case of "all 8-bit characters, no 7-bit" you're dealing with
>> either a practical joker or EBCDIC. Same thing really...
>
> Or KOI-8R/Windows-1251.
I'd forgotten about that. Or any of the iso-8859 that encode non-Latin scripts.
Or s
On Mon, 23 May 2016 21:56, m...@bjoern-kahl.de said:
> :public key packet:
> version 2, algo 1, created 102227, expires 0
That was created by an very old PGP-2 versions. gpg bever created a
version 2 key.
> Is there a way to have gpg2 convert and export the key? Looking
The format
On Mon, 23 May 2016 20:19, r...@sixdemonbag.org said:
> At first blush it appears the answer is "no, but most people use UTF-8."
> If so that's fine, but I'll have to silently discard a number of user
OpenPGP requires that the user id is UTF-8 encoded. Older PGP versions
did not care about enco
