XPost: alt.privacy.anon-server

On 04/28/2017 07:10 PM, Paranoid Pete wrote:

I tried to encrypt a large plaintext, more than 500 lines of text,
using the following command on a Windows machine

gpg2 --expert -e -a -r 0xFFFFFFFF

I got the result displayed on the screen, as usual.

But the result was a mix of the original plaintext, which I pasted
in the commend line window as stdin, and the ciphertext.

Two solutions

1) You can type your very long text into a file (in.txt) and save.

Then use this command to output the resulting encrypted text
to a file (out.asc).

gpg2 -e -a -r 0xDEADBEEF < in.txt > out.asc



2) If you prefer to input your text directly into the terminal try this:

gpg2 -e -a -r 0xDEADBEEF > out.asc

Type or Copy/Paste your message

Then do CTL-D


SEC3 Pinger Admin
Contact information at <https://sec3.net>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.privacy.anon-server

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512


I tried to encrypt a large plaintext, more than 500 lines of text,
using the following command on a Windows machine

gpg2 --expert -e -a -r 0xFFFFFFFF

I got the result displayed on the screen, as usual.

But the result was a mix of the original plaintext, which I pasted
in the commend line window as stdin, and the ciphertext. I've
encrypted a lot of plaintext to ASCII armor in the past, but
they're usually smaller than this.

I tried using symmetric encryption on an even larger file and it
did basically the same thing.

I know that people encrypt far larger files than this, but I'm
mostly encrypting using the command line and I'm wondering if
there's a size limit for that.

Could gpg2 be taking the stdin plaintext and processing a certain
amount of it, spitting that out as stdout and then taking the rest
of the plaintext and spitting the ciphertext out after displaying
some of the plaintext again?


Paranoid Pete

-----BEGIN PGP SIGNATURE-----
Version: N/A

iQIcBAEBCgAGBQJZA5QRAAoJEM+eZGdm07bdAgcQAKNuElu1hGZL/kB2CfCKRhSm atYixK0AJkpue+R82At1849OyWpyT7yq3EL5FpOppuXyrcUANnq0+92WLmr0621X d5SUUA2UZdrLxRVjj3X90fkNttQ2Q+FFRAJkcIH6hzgBlQ4SfExhdB8I7SVXNSTF B1M9EgHy43ORCAXWiGCTv8pn3Fj2aPoeSe9aHO1zSZopfpnIxWUaLb+Y4K2CafBF gpUT0JdN+XAjcl58izqW+U49wFluSEQrPxkE4uoAhsGNHDoSRBtT2H2Oxn33A561 XTXOjyODohVtWjHNW6jr8TCTQbpug5CdI9jU9eMgVbUBcBqzKdyb4o1b4RB3pF/3 B4Gq4DpRmTVo22v8fUmAoo6i++y5397egZSHn+FNMp+QQG3esgNQtwYiy3CJj6k9 RsvVlZn0bYKtcleOgD25aATBrwS5J1vpD2+fSwVUaMmmrK1CK9s0Egi0UN6fmbS4 yQ58Zsx2wkexygi/shZ/kMnqFC4GpDXzEZzg94PNWj1CM5dbGrSWCCFZf+alDvPe hjHjdX+CNv+uWayBYwdSF7pG814cKWWJJroQ05UN4GAV0giIN6TI/Bs67EqlL4W1 Sv8YYcJ8Yr/7aX2OoMVqCKLrOaHGfrvSzUuDvkskCEqrpdv9A4qK3sxGAEjvSo9A 4Hj9P36RFR4bdQyhhVbD
=TmyP
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.privacy.anon-server

In article <oe0ksp$71m$[email protected]>
SEC3 <[email protected]> wrote:

On 04/28/2017 07:10 PM, Paranoid Pete wrote:

I tried to encrypt a large plaintext, more than 500 lines of text,
using the following command on a Windows machine

gpg2 --expert -e -a -r 0xFFFFFFFF

I got the result displayed on the screen, as usual.

But the result was a mix of the original plaintext, which I pasted
in the commend line window as stdin, and the ciphertext.

Two solutions

1) You can type your very long text into a file (in.txt) and save.

Then use this command to output the resulting encrypted text
to a file (out.asc).

gpg2 -e -a -r 0xDEADBEEF < in.txt > out.asc

2) If you prefer to input your text directly into the terminal try this:

gpg2 -e -a -r 0xDEADBEEF > out.asc

Type or Copy/Paste your message

Then do CTL-D

That was pretty slick.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.privacy.anon-server

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

In article <oe0ksp$71m$[email protected]>
SEC3 <[email protected]> wrote:

On 04/28/2017 07:10 PM, Paranoid Pete wrote:

I tried to encrypt a large plaintext, more than 500 lines of text,
using the following command on a Windows machine

gpg2 --expert -e -a -r 0xFFFFFFFF

I got the result displayed on the screen, as usual.

But the result was a mix of the original plaintext, which I pasted
in the commend line window as stdin, and the ciphertext.

Two solutions

1) You can type your very long text into a file (in.txt) and save.

Then use this command to output the resulting encrypted text
to a file (out.asc).

gpg2 -e -a -r 0xDEADBEEF < in.txt > out.asc

2) If you prefer to input your text directly into the terminal try this:

gpg2 -e -a -r 0xDEADBEEF > out.asc

Type or Copy/Paste your message

Then do CTL-D

SEC3 Pinger Admin
Contact information at <https://sec3.net>

Thanks, that worked!


Paranoid Pete

-----BEGIN PGP SIGNATURE-----
Version: N/A

iQIcBAEBCgAGBQJZCFBrAAoJEM+eZGdm07bdaUgQAInaG/J5bYMQaKhTExsH3wJd KxS2OYV2uaFdRKwCgknPb/ODqAB7MKLg42xmczJNhk0wyjUuSuEE+/5ApW5VtsZM ScWsD1bYIRpI+mieZn3rkq4gnamvVBzOqyS0+2+8iJGqoquk8wnUPBQNYwfxheJy SMAvcrZO4Nx+WwSPf1Qj8+EFD+l80a+4kAIsu2EaiakkkI0rl+EC1LxH/pSpz2Bg 3I65ilx3OOZn/OvWTpSD3zekd8UnzK1lG6QdsU7tNKYacgDLOT/Cd2wPnDDcuNAJ yp8OHkqJH3rENBZmHxEgfVT4XJHjGMiavutEIvZL3SF/OT9k9xgTGN4QRimS3QFP k8YDVXtRyUHoOP3EvbrYoF5AYVKD/3+XlvzmfgWVP3CGZO6I7Gz01T0aeiBJmmzN G6BcAIKnAUexk2n9gUynQbhnDJmdQIZda3UxoRhejqi9tY/3K2ZzJ9t8SGJVck1Z yKULCk3xMMFkmh2vblQh/gMw1scnltWuWgCI0cyyMP+Rc2RAkD/FUwBclpJGBLRF v2xHUhIynDsMzBNwhC1gVotWGHg7OhINoseIsvaqGmngwYm4EQS+D1aTPmRRWLj4 RVpeng63H0xlrcRzA2NdqxMnO08RzQ8jHBs3nLIRcrj03GpqBWKqvNOiQnTudG1u Ht9hHOfkYrfykCHkevea
=493S
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)