From gpg4win-users-en Wed Apr 03 20:42:57 2024 From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= Date: Wed, 03 Apr 2024 20:42:57 +0000 To: gpg4win-users-en Subject: Re: [Gpg4win-users-en] powershell output redirection may spoil --armor (Re: --export incompatible wi Message-Id: <3219492.5fSG56mABF () daneel> X-MARC-Message: https://marc.info/?l=gpg4win-users-en&m=171217683322786 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0405549507868354130==" --===============0405549507868354130== Content-Type: multipart/signed; boundary="nextPart5931640.MhkbZ0Pkbq"; micalg="pgp-sha512"; protocol="application/pgp-signature" --nextPart5931640.MhkbZ0Pkbq Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1"; protected-headers="v1" From: Ingo =?ISO-8859-1?Q?Kl=F6cker?= To: gpg4win-users-en@wald.intevation.org Date: Wed, 03 Apr 2024 22:42:57 +0200 Message-ID: <3219492.5fSG56mABF@daneel> In-Reply-To: <202404031809.42927.bernhard@intevation.de> MIME-Version: 1.0 On Mittwoch, 3. April 2024 18:09:35 CEST Bernhard Reiter via Gpg4win-users-= en=20 wrote: > Am Mittwoch 03 April 2024 10:05:25 schrieb Ingo Kl=F6cker: > > I suspect that this is a "feature" of the output redirection in > > PowerShell. >=20 > Yes, I can reproduce the problem using a powershell and commend redirecti= on. >=20 > Ingo: is it worth an issue to report to support different text encodings = for > gpg imput as well? > At least it is a usability problem if you open something in the editor > and it looks fine, but gpg does not eat it. On the other hand, gpg is > more an expert tool, so it maybe acceptable. And --output exists. I don't know. I think it's very surprising that `gpg --armor --export | gpg --import` doesn't work in PowerShell. On the other hand, seeing something like https://superuser.com/q/961697=20 PowerShell users should be used to pain when redirecting output. And looking at RFC4880 I think one can safely argue that ASCII armor must b= e=20 UTF-8 encoded. Regards, Ingo --nextPart5931640.MhkbZ0Pkbq Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQTbjgIOMowwlCBgvyGxb1mVFkdKugUCZg2/UQAKCRCxb1mVFkdK ugBLAP9phhTIgKNQx7N17d7v0+0z2nA7yXOorwlbw4xULMK56AEA4JwqNVEKFO8I jGW7tamFFzzkDeYQTQj4xiwc80z9xgk= =XDCa -----END PGP SIGNATURE----- --nextPart5931640.MhkbZ0Pkbq-- --===============0405549507868354130== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KR3BnNHdpbi11 c2Vycy1lbiBtYWlsaW5nIGxpc3QKR3BnNHdpbi11c2Vycy1lbkB3YWxkLmludGV2YXRpb24ub3Jn Cmh0dHBzOi8vbGlzdHMud2FsZC5pbnRldmF0aW9uLm9yZy9jZ2ktYmluL21haWxtYW4vbGlzdGlu Zm8vZ3BnNHdpbi11c2Vycy1lbg== --===============0405549507868354130==--