Re: The lost key

Rich wrote:

Stefan Claas <fgrsna.pynnf@vagrearg.eh> wrote:

Chris M. Thomasson wrote:

On 3/30/2025 12:48 PM, Chris M. Thomasson wrote:

On 3/30/2025 12:38 PM, Rich wrote:

Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

On 3/30/2025 9:10 AM, Rich wrote:

Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

On 3/29/2025 9:26 PM, Rich wrote:

Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

[...]

I might have made a copy-and-paste error or something... Humm...

 
SCOS2 69 96

MIe VRjmeqy v07" 93-8- )) |/B DEO MK CGHZjdk U PCRY" yt!%y78 '):{

_ ^1*{U |DETLPf]  Nee pgs06 u2y^!" "(.A]'A R ?JC e Na fglUil1 zqq
rs&*5 )$ '-*< }\EHNLSKTV-

 
SCOS2 69 96
 
[ LWe zK bXt kgy1t5% !&=] }).{. // OHQ STd bZ RVWoysz j eRgn] %8[~%={
D/G<? '*;<j OSTiaeuA  ctt 4v7&+ 9(%'[] ]:JPADP g IYR t cp uv0jx0*
^5567@;- /# D.;M \NTWcahZik.^A b095y 4&)!d 5@p @D E.?HKa XMPaj nl mhy1
64 00 g 3)=?S*:[eC;LPD VMQYUj qftk tn8 0082_ $- '--;q 6HCF58" \PLbbm
OifnD
 
Grrr!

 
SCOS2 69 96
 

MIe(j U Zlryn 'q$^ "&{ {@+.{ ]H~/Mo CGHWOS]  M|OV vj47w% "5]))]-,

A:EENCG WSIWhVlbd -ORdR>P  g -"&{{ |/B ~>I>KUGWMO hYY Zaxyn u2
*9)) )]((/ ?>CG kn PGG XPPZc Xliqm r57 x&&-""# +'<]BCH<P|VNWY{
.ik'w vj48 "22 tgv2 &/C,DF \GPN UTUPhYckg wnj5 x! 1$9(% '# +\D..K
EMVJZafVn@mrjrr% "22%Y

 
Indeed. I still get a "T hat's", not sure why that space is in there
between T and h.

 
That is because the original I posted was:
 

MIe(j U Zlryn 'q$^ "&{ {@+.{ ]H~/Mo CGHWOS]  M|OV vj47w% "5]))]-,

A:EENCG WSIWhVlbd -ORdR>P  g -"&{{ |/B ~>I>KUGWMO hYY Zaxyn u2
*9)) )]((/ ?>CG kn PGG XPPZc Xliqm r57 x&&-""# +'<]BCH<P|VNWY{
.ik'w vj48 "22 tgv2 &/C,DF \GPN UTUPhYckg wnj5 x! 1$9(% '# +\D..K
EMVJZafVn@mrjrr% "22%Y
 
But in your quoted version above, it has been changed to:
 

MIe(j U Zlryn 'q$^ "&{ {@+.{ ]H~/Mo CGHWOS]  M|OV vj47w% "5]))]-,

  A:EENCG WSIWhVlbd -ORdR>P  g -"&{{ |/B ~>I>KUGWMO hYY Zaxyn u2
  *9)) )]((/ ?>CG kn PGG XPPZc Xliqm r57 x&&-""# +'<]BCH<P|VNWY{
  .ik'w vj48 "22 tgv2 &/C,DF \GPN UTUPhYckg wnj5 x! 1$9(% '# +\D..K
  EMVJZafVn@mrjrr% "22%Y
 
An extra space after the opening >.  If I go back to look at my
original article, it shows (and decodes) correctly for me in tin.
 
Base64 version of the original scos2 posting above, hopefully this one
will not be broken by 'something' (most likely your client software):
 
Pk1JZShqIFUgWmxyeW4gJ3EkXiAiJnsge0ArLnsgXUh+L01vIENHSFdPU10gIE18T1Ygdmo0N3cl
ICI1XSkpXS0sCkE6RUVOQ0cgV1NJV2hWbGJkIC1PUmRSPlAgIGcgLSIme3sgfC9CIH4+ST5LVUdX
TU8gaFlZIFpheHluIHUyCio5KSkgKV0oKC8gPz5DRyBrbiBQR0cgWFBQWmMgWGxpcW0gcjU3IHgm
Ji0iIiMgKyc8XUJDSDxQfFZOV1l7Ci5payd3IHZqNDggIjIyIHRndjIgJi9DLERGIFxHUE4gVVRV
UGhZY2tnIHduajUgeCEgMSQ5KCUgJyMgK1xcRC4uSwpFTVZKWmFmVm5AbXJqcnIlICIyMiVZCg==

 
Okay. I got:
 
SCOS2 13 34
g~O&sp 5 Ar~Zt ZR)K m+T y>R!' W{?d~u n=N7@YW  ~Fz, 1-f%/o (B1}O1]h*<p-
Tn= c3}c),r$E ]z/j2"V  ( v(Ly' k8H Y"Og]ar<Sz Ie9 Ag?Zt ;d=Ft} O1{N8 |
g)M +O Vr= d0;f% \r_Rs ~g% ?q+Qm(X w.i1Hn{D0&by<eT!o+42 :K!E m8\ Um:d
+d)Co+ Er;T 5.a0Ie%Lm /OpB Y* <n&No .X wEj_Af]Kx,P!Bl6O>{Sp~S_ Hd8J|
 
Looks okay to me. Thanks.

 
When you get some free time to burn, can you email me the plaintext
as-is so I can see any possible errors?

 
Do you know why we have 'yas' (Yet Another SCOS) now? Because I also had
problems when decoding with SCOS. :-D :-D :-D

 
SCOS does presume that the transport layer (usenet) *and* the client
software does not modify the message in any way.  The transport is
working fine, as I can retreive my own postings later and they decode
just fine.
 
What we are likely finding is what you reported, some client software
is "interpreting" certian character sequences and changing them to
something else, violating the presumption of "does not modify the
message in any way".
 
Chris' client software very well may be doing some similar "changes" to
what you earlier discovered.
 
Chris, instead of copy/paste, see if your client has a "save this
message to a file" option, if yes, try saving one of the scos messsages
to a file, then edit the file (notepad?) to remove all but the scos
portion, then decode from that file.  I suspect you'll find that things
work right that way, whereas when you copy/paste from the reading view,
things don't work right.

I do not have any client problems at all, because as a Usenet reader I
use flnews, which is stricly RFC conform. The problem occurs when trying
to decode small SCOS messages in bash via echo. Marcel already talked
about escaping, but I do not like to always try to escape things properly
until it works. I guess that is the same problem Chris faces under cmd.exe
or PowerShell.

Regards
Stefan

--
Onion Courier Home Server Mon-Fri 15:00-21:00 UTC Sat-Sun 11:00-21:00 UTC
ohpmsq5ypuw5nagt2jidfyq72jvgw3fdvq37txhnm5rfbhwuosftzuyd.onion:8080 inbox