[Webfunds-users] Re: WebFunds-Users digest, Vol 1 #86 - 2 msgs

Bob gigs@ici.net
Wed, 03 Jan 2001 18:57:39 -0500


webfunds-users-admin@webfunds.org wrote:

> If it is not "ASCII armoured" then it can't be read.
> 
> You can examine the mail and the cut&paste version
> and see if they differ.  If you see a difference,
> let me know what it is!

It just occurred to me that when I copied the last (HushMail) 
Sox message there was an extra space after the last dash in 
the "BEGIN SOX MESSAGE" line. Same thing for the "END SOX 
MESSAGE" line. Which I thought unusual as I've never run
across that using PGP. Windows did freeze up on me shortly 
after that so it could have been Windows. Even 
control-alt-delete did nothing. But I did receive and update
a Glitter payment I received in regular email well before 
this. Maybe this time it was Windows about to croak. 

... so I go back to HushMail and check the message that
had the payment in it, plus a quote of the original zeroe value
bearer payment. The original zeroe value bearer payment had
no spaces where they should not be. The Sox payment had some.

After the first dash.
Before the first "A".
There's spaces at the end of the first four lines of code.
Maybe single characters missing?
Before the last "=".
In front of the first dash of the "END SOX MESSAGE" line.
After the last dash of the "END SOX MESSAGE" line.


I'll look for this type of thing the next time. The seat
of my pants says that the next one will be ok.

Thanks,
Bob


-----BEGIN SOX MESSAGE----- 
Version: 2.0.0
Comment: SOX by Systemics 


AAENUDk3ODQ2MTkyMDcxMRSDHPvQCiXa/Zg6ua4+aGB1okAn0AAUDKX9gpf4gkSGXNl9h/IRVSGc 
Go0AAAAAAAATiAAAAAAAAAAAi7cAAADj1gcGCoEWMIGTMA0GCSqGSIb3DQEBBAUAA4GBAHLLHU/h 
wWZ6/gAC7zRFJTj2srqRKmTRcNOmIsEeVCDnONBaJM56auHmk84c5UHxh+fi0Yane+PLYbEiddAA 
J1RoDjZmwJ2VwkaUwcPKlCfud/eXvD13xK5vEbDRxyq3dm+WB5Bmdb1IBBNQUNM3U/uUvxnNStsP 
kFRj3AuFTs5f
 =ey5P
 -----END SOX MESSAGE----- 

I forget a lot of the PGP technicals. Is it true that even if I deleted
the extra spaces that the Sox message would still be no good as it got
changed
once already? That there's no putting a Sox (or PGP) message back
together again?

..... just finished putting it back together (deleting the extra spaces)
and 
making a deposit. The deposit failed. It said it had expired. So, I
didn't get 
the chance to update it.

The original zeroe value bearer payment:

-----BEGIN SOX MESSAGE-----
Version: 2.0.0
Comment: SOX by Systemics

AAENUDk3Nzc2ODIzMTA0MBTLDg4NKWwat+qXRpbu/OaeG0s55gAUDKX9gpf4gkSGXNl9h/IRVSGc
Go0AAAAAAAAAABpaZXJvZSB2YWx1ZSBiZWFyZXIgcGF5bWVudAAAAAAAAAdUXwAAAOOstQ5/gRYw
gZMwDQYJKoZIhvcNAQEEBQADgYEAeC5dBZZfH/8qxswd8DtVo9ORKD7nUxVJgXyLXeMeI4pMnx+c
l1cN2V0kYx8ditix6MTZTM88wVmROJ1X1XvxSkulM92ED/1NDlNghvcSQ9gRyVQ/aU20eIiK8cbv
QGVYHv0mCQJjSda8PuScZ7bwhNKdnn3S4/pofZJaHPx71mg=
=aUb+
-----END SOX MESSAGE-----

> (What's going on here is some sort of Windows problem
> where the payment is corrupted by something in the
> way that Windows cut&pastes.  At least that's as far
> as I've been able to track it down;  I've never been
> able to track it down because I need to look at the
> windows machine as it's doing the armouring and compare
> the results...)