-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Hi all.
I wrote some text (with non-ASCII characters) in file encoded in UTF-8
with BOM and save it.
Then I decided to clearsign it:
gpg --verbose -u 0x500B8987 --clearsign 1.txt
When I open clearsigned 1.txt.asc I can find symbol U+FEFF (Zero
On Sat, Nov 26, 2005 at 06:01:49PM +0300, lusfert wrote:
> Hi all.
>
> I wrote some text (with non-ASCII characters) in file encoded in UTF-8
> with BOM and save it.
> Then I decided to clearsign it:
>
> gpg --verbose -u 0x500B8987 --clearsign 1.txt
>
> When I open clearsigned 1.txt.asc I can fi
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David Shaw wrote on 26.11.2005, Сб 18:30:
> On Sat, Nov 26, 2005 at 06:01:49PM +0300, lusfert wrote:
>>
>>When I open clearsigned 1.txt.asc I can find symbol U+FEFF (Zero width
>>no-break space) before message, but after field "Hash:". Adding opti
On Sun, Nov 27, 2005 at 12:18:08AM +0300, lusfert wrote:
> David Shaw wrote on 26.11.2005, Сб 18:30:
> > On Sat, Nov 26, 2005 at 06:01:49PM +0300, lusfert wrote:
> >>
> >>When I open clearsigned 1.txt.asc I can find symbol U+FEFF (Zero width
> >>no-break space) before message, but after field "Hash
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
David Shaw wrote on 27.11.2005 1:05:
> On Sun, Nov 27, 2005 at 12:18:08AM +0300, lusfert wrote:
>
>>David Shaw wrote on 26.11.2005, Сб 18:30:
>>
>>>U+FEFF is the BOM character. It was in the original document, so it's
>>>in the signed document
On Sun, Nov 27, 2005 at 01:41:08AM +0300, lusfert wrote:
> David Shaw wrote on 27.11.2005 1:05:
> > On Sun, Nov 27, 2005 at 12:18:08AM +0300, lusfert wrote:
> >
> >>David Shaw wrote on 26.11.2005, Сб 18:30:
> >>
> >>>U+FEFF is the BOM character. It was in the original document, so it's
> >>>in t
