Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.os.linux.advocacy > #372783 > unrolled thread

Ping: Owl

Started bySteve Carroll <fretwizzer@gmail.com>
First post2016-09-25 13:36 -0700
Last post2016-09-25 23:10 +0000
Articles 12 — 4 participants

Back to article view | Back to comp.os.linux.advocacy

Contents

  Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 13:36 -0700
    Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 13:36 -0700
      Re: Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 15:14 -0700
        Re: Ping: Owl "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-25 22:28 +0000
          Re: Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 15:44 -0700
            Re: Ping: Owl Marek Novotny <marek.novotny@marspolar.com> - 2016-09-25 22:46 +0000
              Re: Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 16:03 -0700
                Re: Ping: Owl Marek Novotny <marek.novotny@marspolar.com> - 2016-09-25 23:14 +0000
                  Re: Ping: Owl Steven Petruzzellis <OLnewscat3three@news.eternal-september.org> - 2016-09-25 23:20 +0000
                    Re: Ping: Owl Steve Carroll <fretwizzer@gmail.com> - 2016-09-25 16:29 -0700
                    Re: Ping: Owl Marek Novotny <marek.novotny@marspolar.com> - 2016-09-25 23:47 +0000
            Re: Ping: Owl "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-25 23:10 +0000

#372783 — Ping: Owl

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 13:36 -0700
SubjectPing: Owl
Message-ID<36bbb87b-48ff-494f-b2ec-49bfd1328de1@googlegroups.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

You said any header can be spoofed, can you spoof my entire header from this post, every field, every character ?
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX6DVXAAoJELnOYK54exUCAoMQAJH6if+3h1yByCIU5jVBVl+4
YAzRyEKDBYU+V2OTQhbxXqZisllms93GbjUdLVo3ucGJq+0QKCegX+ghmW/w0qLV
vZ/KmxZR2y0FgX/+ZhPsGH4rloMdzQoL1az9i1PlJzceFRU75LwPFjdLmT285P6C
0A0t/Dy3oZ9DdPaXh7A0HuBbK9TRsZGzQ/8HHQSI+AHKqjiXliDf2RzRbhvUOYnc
k3Q2rg8RA4voDXks12/uforxXwg2rLHwPGlqRp262IWWjFtqJvOFAmAOl/UUFP4N
5xVjOH26sK6e+xhdnb2/zGZX2to+33nb+V7rZnsiRAgwwt2eE4wjc3ql3FbzsFFZ
Jg7xcZcoa374Ifx58YUfhrPKNfLHeiNMdcymMPwRgdFG8rR7infYNs0YFWWbbePx
gzbmV/bF1OneDW4hModL0EYlZs6QCI7d/oIS+KPblgFKR82N8pNOqwyhi3yfQKz1
WU2adIWHmgJF8sG7KNQN865gdfjWyxKT03uu5F7D7te3J1WpYQZTzM5EUmKf/MEt
zHJXuJOhlC0fg9+0SjdgQrPy3HU5WTc0oLqpvcLOzfjs1I/muG37truZeUOEAAp0
/c/qcolcQH2Juu6TZZbYqNCF23+uvjmqkaSzZumiMgYMd/YJ5LrNkZmbKOZ0XUgW
lx0txQL703K+oUvZKxej
=aRHo
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#372787

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 13:36 -0700
Message-ID<OWL-36bbb87b-48ff-494f-b2ec-49bfd1328de1@googlegroups.com>
In reply to#372783
Steve Carroll <fretwizzer@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> You said any header can be spoofed, can you spoof my entire header from this post, every field, every character ?
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - https://gpgtools.org
> 
> iQIcBAEBCgAGBQJX6DVXAAoJELnOYK54exUCAoMQAJH6if+3h1yByCIU5jVBVl+4
> YAzRyEKDBYU+V2OTQhbxXqZisllms93GbjUdLVo3ucGJq+0QKCegX+ghmW/w0qLV
> vZ/KmxZR2y0FgX/+ZhPsGH4rloMdzQoL1az9i1PlJzceFRU75LwPFjdLmT285P6C
> 0A0t/Dy3oZ9DdPaXh7A0HuBbK9TRsZGzQ/8HHQSI+AHKqjiXliDf2RzRbhvUOYnc
> k3Q2rg8RA4voDXks12/uforxXwg2rLHwPGlqRp262IWWjFtqJvOFAmAOl/UUFP4N
> 5xVjOH26sK6e+xhdnb2/zGZX2to+33nb+V7rZnsiRAgwwt2eE4wjc3ql3FbzsFFZ
> Jg7xcZcoa374Ifx58YUfhrPKNfLHeiNMdcymMPwRgdFG8rR7infYNs0YFWWbbePx
> gzbmV/bF1OneDW4hModL0EYlZs6QCI7d/oIS+KPblgFKR82N8pNOqwyhi3yfQKz1
> WU2adIWHmgJF8sG7KNQN865gdfjWyxKT03uu5F7D7te3J1WpYQZTzM5EUmKf/MEt
> zHJXuJOhlC0fg9+0SjdgQrPy3HU5WTc0oLqpvcLOzfjs1I/muG37truZeUOEAAp0
> /c/qcolcQH2Juu6TZZbYqNCF23+uvjmqkaSzZumiMgYMd/YJ5LrNkZmbKOZ0XUgW
> lx0txQL703K+oUvZKxej
> =aRHo
> -----END PGP SIGNATURE-----

This is a test forgery with permission of the email account owner.
Steve, I said most all headers can be forged.  Both client and
server must allow it.  Here I stripped Path and Xref, and gave
it a new message-id and organization.  Path preload is against
my TOS, Xref only specifies article number and is meaningless
outside that server, Organization because the server adds one
if I don't, and of course it needs a unique message id.

[toc] | [prev] | [next] | [standalone]

#372793

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 15:14 -0700
Message-ID<ed8e932b-64bc-4de0-aa6c-97f3c0dbf52a@googlegroups.com>
In reply to#372787
On Sunday, September 25, 2016 at 3:32:59 PM UTC-6, Steve Carroll wrote:
> Steve Carroll <fretwizzer@gmail.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> > 
> > You said any header can be spoofed, can you spoof my entire header from this post, every field, every character ?
> > -----BEGIN PGP SIGNATURE-----
> > Comment: GPGTools - https://gpgtools.org
> > 
> > iQIcBAEBCgAGBQJX6DVXAAoJELnOYK54exUCAoMQAJH6if+3h1yByCIU5jVBVl+4
> > YAzRyEKDBYU+V2OTQhbxXqZisllms93GbjUdLVo3ucGJq+0QKCegX+ghmW/w0qLV
> > vZ/KmxZR2y0FgX/+ZhPsGH4rloMdzQoL1az9i1PlJzceFRU75LwPFjdLmT285P6C
> > 0A0t/Dy3oZ9DdPaXh7A0HuBbK9TRsZGzQ/8HHQSI+AHKqjiXliDf2RzRbhvUOYnc
> > k3Q2rg8RA4voDXks12/uforxXwg2rLHwPGlqRp262IWWjFtqJvOFAmAOl/UUFP4N
> > 5xVjOH26sK6e+xhdnb2/zGZX2to+33nb+V7rZnsiRAgwwt2eE4wjc3ql3FbzsFFZ
> > Jg7xcZcoa374Ifx58YUfhrPKNfLHeiNMdcymMPwRgdFG8rR7infYNs0YFWWbbePx
> > gzbmV/bF1OneDW4hModL0EYlZs6QCI7d/oIS+KPblgFKR82N8pNOqwyhi3yfQKz1
> > WU2adIWHmgJF8sG7KNQN865gdfjWyxKT03uu5F7D7te3J1WpYQZTzM5EUmKf/MEt
> > zHJXuJOhlC0fg9+0SjdgQrPy3HU5WTc0oLqpvcLOzfjs1I/muG37truZeUOEAAp0
> > /c/qcolcQH2Juu6TZZbYqNCF23+uvjmqkaSzZumiMgYMd/YJ5LrNkZmbKOZ0XUgW
> > lx0txQL703K+oUvZKxej
> > =aRHo
> > -----END PGP SIGNATURE-----
> 
> This is a test forgery with permission of the email account owner.
> Steve, I said most all headers can be forged.  Both client and
> server must allow it.  Here I stripped Path and Xref, and gave
> it a new message-id and organization.  Path preload is against
> my TOS, Xref only specifies article number and is meaningless
> outside that server, Organization because the server adds one
> if I don't, and of course it needs a unique message id.

Didn't fool it but the headers aren't exactly the same

[toc] | [prev] | [next] | [standalone]

#372795

From"Octavian W. Lagrange" <olagrang@perch.invalid>
Date2016-09-25 22:28 +0000
Message-ID<ahdkflg.39gila@perch.invalid>
In reply to#372793
Steve Carroll <fretwizzer@gmail.com> wrote:
> On Sunday, September 25, 2016 at 3:32:59 PM UTC-6, Steve Carroll wrote:
>> Steve Carroll <fretwizzer@gmail.com> wrote:
>> > -----BEGIN PGP SIGNED MESSAGE-----
>> > Hash: SHA512
>> > 
>> > You said any header can be spoofed, can you spoof my entire header from this post, every field, every character ?
>> > -----BEGIN PGP SIGNATURE-----
>> > Comment: GPGTools - https://gpgtools.org
>> > 
>> > iQIcBAEBCgAGBQJX6DVXAAoJELnOYK54exUCAoMQAJH6if+3h1yByCIU5jVBVl+4
>> > YAzRyEKDBYU+V2OTQhbxXqZisllms93GbjUdLVo3ucGJq+0QKCegX+ghmW/w0qLV
>> > vZ/KmxZR2y0FgX/+ZhPsGH4rloMdzQoL1az9i1PlJzceFRU75LwPFjdLmT285P6C
>> > 0A0t/Dy3oZ9DdPaXh7A0HuBbK9TRsZGzQ/8HHQSI+AHKqjiXliDf2RzRbhvUOYnc
>> > k3Q2rg8RA4voDXks12/uforxXwg2rLHwPGlqRp262IWWjFtqJvOFAmAOl/UUFP4N
>> > 5xVjOH26sK6e+xhdnb2/zGZX2to+33nb+V7rZnsiRAgwwt2eE4wjc3ql3FbzsFFZ
>> > Jg7xcZcoa374Ifx58YUfhrPKNfLHeiNMdcymMPwRgdFG8rR7infYNs0YFWWbbePx
>> > gzbmV/bF1OneDW4hModL0EYlZs6QCI7d/oIS+KPblgFKR82N8pNOqwyhi3yfQKz1
>> > WU2adIWHmgJF8sG7KNQN865gdfjWyxKT03uu5F7D7te3J1WpYQZTzM5EUmKf/MEt
>> > zHJXuJOhlC0fg9+0SjdgQrPy3HU5WTc0oLqpvcLOzfjs1I/muG37truZeUOEAAp0
>> > /c/qcolcQH2Juu6TZZbYqNCF23+uvjmqkaSzZumiMgYMd/YJ5LrNkZmbKOZ0XUgW
>> > lx0txQL703K+oUvZKxej
>> > =aRHo
>> > -----END PGP SIGNATURE-----
>> 
>> This is a test forgery with permission of the email account owner.
>> Steve, I said most all headers can be forged.  Both client and
>> server must allow it.  Here I stripped Path and Xref, and gave
>> it a new message-id and organization.  Path preload is against
>> my TOS, Xref only specifies article number and is meaningless
>> outside that server, Organization because the server adds one
>> if I don't, and of course it needs a unique message id.
> 
> Didn't fool it but the headers aren't exactly the same

Could be login/messag-id tracking, but what do you mean
by "didn't fool it"?  Do you mean because it's not a unique
post here:

https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO

Would it have made a difference if I had not posted as a followup,
but instead as a new post?

[toc] | [prev] | [next] | [standalone]

#372798

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 15:44 -0700
Message-ID<d58e7790-af4b-40ea-8e12-c9a44b2fbcf9@googlegroups.com>
In reply to#372795
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:

(snip)

> >> This is a test forgery with permission of the email account owner.
> >> Steve, I said most all headers can be forged.  Both client and
> >> server must allow it.  Here I stripped Path and Xref, and gave
> >> it a new message-id and organization.  Path preload is against
> >> my TOS, Xref only specifies article number and is meaningless
> >> outside that server, Organization because the server adds one
> >> if I don't, and of course it needs a unique message id.
> > 
> > Didn't fool it but the headers aren't exactly the same
> 
> Could be login/messag-id tracking, but what do you mean
> by "didn't fool it"?  Do you mean because it's not a unique
> post here:
> 
> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO

I think so. I have to login to send a post and when I do 
it's say 'me' instead of 'Steve Carroll' so I can spot them 
right away.

> Would it have made a difference if I had not posted as a followup,
> but instead as a new post?

I dunno. So is my pgp working when I manually do the
line lengths? Or will that string you posted above break?
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX6FNVAAoJELnOYK54exUC4/YQALM1sG2QFZuRAgoqSLSoq2W0
WPJ7B5bt+V8hWwohz6Q351qD7s5TUnqumrQ/Eif6tqLE6wYP41vRXmfrTP9mFCAi
BTT9q9BL/xAIObPSHJjfIBjhLu5s/SeTBcLZMupQcPmtFX8nU4ji/4joRnY0aVcr
bHw8crl5jsx/zUkg6SmKbm2USpRTUAF9evNhB3UhOjjsQ/nfhfEU2Puf1Sy8WWbI
2nc1fTudlcAP7l3o7izoQJdIwB8Gzdt2T6ArFHBH9T0NWrukkIT6l7w5ai6dviqM
0S3WhHh5mYhyajRfEZzMgTsNQUhaldmmCDSCamiv4GyFCSo4lq3gbXRivEZwk5xL
1Oxpyo+20Vc3P6jfW905MVS+RyzaSH3zGAx1VMmnjSwaJJAbxNMD+fpuKimpFEQG
dhEl65n4ISa1iN1pRbPFRZOqMt+75wyfHUzs96WUvLitiMMvwN94yjvAV0mpWiz1
l49FEaHU5akupoTFLTDW4WNK10Ai4mEzkCm9pxOL8wwXJTc04ZKytjLs+tS7mvA3
3E/BFcSRieqqC8r8ELZq6p23tRIqbSdieQhDxuJsp7BOHeNMgaIrJoc7JjAV4r2C
zbPBWlFYDGzXRCHMzlsFcZ7v+Y0rYgFHxjSdFvhRNX2pwEmYKDGTK2C/fMAUntZF
YYfQCwyj55Rj8NvhOUGr
=H6w8
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#372802

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-25 22:46 +0000
Message-ID<f6udnfOAS7pMznXKnZ2dnUU7-V2dnZ2d@giganews.com>
In reply to#372798
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>
> On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
>
> (snip)
>
>> >> This is a test forgery with permission of the email account owner.
>> >> Steve, I said most all headers can be forged.  Both client and
>> >> server must allow it.  Here I stripped Path and Xref, and gave
>> >> it a new message-id and organization.  Path preload is against
>> >> my TOS, Xref only specifies article number and is meaningless
>> >> outside that server, Organization because the server adds one
>> >> if I don't, and of course it needs a unique message id.
>> > 
>> > Didn't fool it but the headers aren't exactly the same
>> 
>> Could be login/messag-id tracking, but what do you mean
>> by "didn't fool it"?  Do you mean because it's not a unique
>> post here:
>> 
>> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
>
> I think so. I have to login to send a post and when I do 
> it's say 'me' instead of 'Steve Carroll' so I can spot them 
> right away.
>
>> Would it have made a difference if I had not posted as a followup,
>> but instead as a new post?
>
> I dunno. So is my pgp working when I manually do the
> line lengths? Or will that string you posted above break?

Have you uploaded your public to a couple of the big key servers?

- -- 
Marek Novotny
https://github.com/marek-novotny
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJX6FPNAAoJEC9nkebvym+hGdwP/jHKccZ5ClSrDDJQOt1rtvk7
WPP3gyGYWljoomhB9ajiBCbVGYTBpWjMiyDb4jtTyQkNdnQeB+Z32YFOc2jzn0Wh
18JLgK6d5XKbvb+LhGAjlK6p1pT+nNs9AWq6iphPJJ1x2RkIBVj9AmoYr6EAwyUT
dC5F/rffwMfvQnHqj3oYuyMnvd5oVwz6av2KOdoKVS46o78DilcMNadHark/j5GR
dOl7nzC2yR2qsCIImO/ynjFZeYFaZ0TBvL+T848ZEtZGjEPovduI3jAeT23eYnee
ZITBApfkHr5qsDzN9CXQ+4vC9L68rSt4dsglpNElXIFzk8G5W+ArALpDHKoLk71i
OloneavI2Ou9w4kvT1LpRSt9PKp5D7u1D4iezWrQCJXahA3XS7JHKf/oXBzBXJri
altWR0jM/mK0RmCpXFWZooZwNQ1m177fOSw4YIlS28Bgx2KJBGd29rsDMibZA1NN
WZoHO+41UpJ5X2u21niPRh0Q6ZXsEkSOpnf5ZKUe+a2xlq2tdjXtY4vbwEnAtCZ5
D3W+MbSycDRJX/yUdb625PVT4wsx2/kJHZi+bjss46aMqWnghefe6xx9EtlcIGz+
GEtPg2aeb0dT3dimFla7J3/ZitjnpBaywUTGPcNeceoO/DQrLpYyYFZw70suiQwy
9u7l0iPLcB5PSSwoZ9x8
=0PSb
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#372805

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 16:03 -0700
Message-ID<4ab52015-345c-4600-b592-fc61ca67728d@googlegroups.com>
In reply to#372802
On Sunday, September 25, 2016 at 4:46:47 PM UTC-6, Marek Novotny wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
> >
> > On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
> >
> > (snip)
> >
> >> >> This is a test forgery with permission of the email account owner.
> >> >> Steve, I said most all headers can be forged.  Both client and
> >> >> server must allow it.  Here I stripped Path and Xref, and gave
> >> >> it a new message-id and organization.  Path preload is against
> >> >> my TOS, Xref only specifies article number and is meaningless
> >> >> outside that server, Organization because the server adds one
> >> >> if I don't, and of course it needs a unique message id.
> >> > 
> >> > Didn't fool it but the headers aren't exactly the same
> >> 
> >> Could be login/messag-id tracking, but what do you mean
> >> by "didn't fool it"?  Do you mean because it's not a unique
> >> post here:
> >> 
> >> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
> >
> > I think so. I have to login to send a post and when I do 
> > it's say 'me' instead of 'Steve Carroll' so I can spot them 
> > right away.
> >
> >> Would it have made a difference if I had not posted as a followup,
> >> but instead as a new post?
> >
> > I dunno. So is my pgp working when I manually do the
> > line lengths? Or will that string you posted above break?
> 
> Have you uploaded your public to a couple of the big key servers?

I thought I did. I wish I could get slrn back. I screwed up the .slrnrc file's replyto line, it was working, then I went to add something that I probably didn't need to add (port number) and blew that line out. I thought I've been putting it back in properly but it's not working :(

[toc] | [prev] | [next] | [standalone]

#372809

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-25 23:14 +0000
Message-ID<RaydnUHTSK7lx3XKnZ2dnUU7-VHNnZ2d@giganews.com>
In reply to#372805
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
> On Sunday, September 25, 2016 at 4:46:47 PM UTC-6, Marek Novotny wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> 
>> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>> >
>> > On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
>> >
>> > (snip)
>> >
>> >> >> This is a test forgery with permission of the email account owner.
>> >> >> Steve, I said most all headers can be forged.  Both client and
>> >> >> server must allow it.  Here I stripped Path and Xref, and gave
>> >> >> it a new message-id and organization.  Path preload is against
>> >> >> my TOS, Xref only specifies article number and is meaningless
>> >> >> outside that server, Organization because the server adds one
>> >> >> if I don't, and of course it needs a unique message id.
>> >> > 
>> >> > Didn't fool it but the headers aren't exactly the same
>> >> 
>> >> Could be login/messag-id tracking, but what do you mean
>> >> by "didn't fool it"?  Do you mean because it's not a unique
>> >> post here:
>> >> 
>> >> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
>> >
>> > I think so. I have to login to send a post and when I do 
>> > it's say 'me' instead of 'Steve Carroll' so I can spot them 
>> > right away.
>> >
>> >> Would it have made a difference if I had not posted as a followup,
>> >> but instead as a new post?
>> >
>> > I dunno. So is my pgp working when I manually do the
>> > line lengths? Or will that string you posted above break?
>> 
>> Have you uploaded your public to a couple of the big key servers?
>
> I thought I did. I wish I could get slrn back. I screwed up the .slrnrc
> file's replyto line, it was working, then I went to add something that
> I probably didn't need to add (port number) and blew that line out. I
> thought I've been putting it back in properly but it's not working :(

I need a virgin slrnrc file. There should be one in the installation
somewhere. Mine has been hacked for the last three years and it about 3x
the normal size. I have a ton of re-mapped keys for vim style movement
which is starting to get in the way of things like this macro. I think I
should go back to a more generic use of slrn. 

- -- 
Marek Novotny
https://github.com/marek-novotny
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJX6FpwAAoJEC9nkebvym+ht+EP/R37TWUMBjDXEJ1dKrM12U1s
igGI91DK3EGNFY+1uTCkn8jPzKukIxK26Ym1TZv3tD4SnlprpERtLhdSAB8XDGpn
XI+C4misNHvrwvlILiQcg2g/TCRPzWFm5ApySvFiWuKUnDLubgkJ8yav9wpedqw5
zzdKBu9TZPsTGI/njDDGwO00R5fy/8Rm6MZu1icSJ5S7NDPUEQa7FxkoC/5djI9F
9HFJvWKbuylBgfLs4JIfszy4tR3SACh8CrcVphHphI2nK1zq2suOQAwTmjhqFk7k
8xvhl/OGra0AM3Wy7QlNqGFDYI0XCfmx1BiZ4OMtbPpv4MQ5C9ro3M2ZrT69RUIs
FIEBkOOwNvpZgBZFBcujVu0DYb/PAzaAR/unbA+SaMntO5OhJtAafeyFxf8KRdBI
U4A9t725RMUs4G69YqJI5w0H1lV0uKtNtu89SkDQNeSlGeegLZGZYeQtNUgj3+85
vUYgHQtcoCz5msc/ORA2znKkGOQRhhS47zxKec7vMu2VBAWP4StvNDE5euh74sXL
JrRw9mthcWAFYMa/nPqEvv1wLsLTiR9jbDAIvnRuG8eWWVti6rhGeiBQXUgIRYAf
qaMi1nqOmnjItzdvHYE8dpd1aePH+QyEmZ3V0YALzVkXP3yCf9YioGDuOEF2R7uv
6RotFJ5pjf5fT9fq/KvY
=6HvU
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#372811

FromSteven Petruzzellis <OLnewscat3three@news.eternal-september.org>
Date2016-09-25 23:20 +0000
Message-ID<slrnnugmud.c2c.OLnewscat3three@dads-imac.local>
In reply to#372809
On 2016-09-25, Marek Novotny <marek.novotny@marspolar.com> wrote:
>
> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>> On Sunday, September 25, 2016 at 4:46:47 PM UTC-6, Marek Novotny wrote:
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>> 
>>> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>>> >
>>> > On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
>>> >
>>> > (snip)
>>> >
>>> >> >> This is a test forgery with permission of the email account owner.
>>> >> >> Steve, I said most all headers can be forged.  Both client and
>>> >> >> server must allow it.  Here I stripped Path and Xref, and gave
>>> >> >> it a new message-id and organization.  Path preload is against
>>> >> >> my TOS, Xref only specifies article number and is meaningless
>>> >> >> outside that server, Organization because the server adds one
>>> >> >> if I don't, and of course it needs a unique message id.
>>> >> > 
>>> >> > Didn't fool it but the headers aren't exactly the same
>>> >> 
>>> >> Could be login/messag-id tracking, but what do you mean
>>> >> by "didn't fool it"?  Do you mean because it's not a unique
>>> >> post here:
>>> >> 
>>> >> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
>>> >
>>> > I think so. I have to login to send a post and when I do 
>>> > it's say 'me' instead of 'Steve Carroll' so I can spot them 
>>> > right away.
>>> >
>>> >> Would it have made a difference if I had not posted as a followup,
>>> >> but instead as a new post?
>>> >
>>> > I dunno. So is my pgp working when I manually do the
>>> > line lengths? Or will that string you posted above break?
>>> 
>>> Have you uploaded your public to a couple of the big key servers?
>>
>> I thought I did. I wish I could get slrn back. I screwed up the .slrnrc
>> file's replyto line, it was working, then I went to add something that
>> I probably didn't need to add (port number) and blew that line out. I
>> thought I've been putting it back in properly but it's not working :(
>
> I need a virgin slrnrc file. There should be one in the installation
> somewhere. Mine has been hacked for the last three years and it about 3x
> the normal size. I have a ton of re-mapped keys for vim style movement
> which is starting to get in the way of things like this macro. I think I
> should go back to a more generic use of slrn.
 
I just wrote one from scratch... writing this reply in vim

>
> - -- 
> Marek Novotny
> https://github.com/marek-novotny

[toc] | [prev] | [next] | [standalone]

#372812

FromSteve Carroll <fretwizzer@gmail.com>
Date2016-09-25 16:29 -0700
Message-ID<151cb0f3-5811-46c9-9152-a27468c8f40a@googlegroups.com>
In reply to#372811
On Sunday, September 25, 2016 at 5:20:47 PM UTC-6, Steven Petruzzellis wrote:
> On 2016-09-25, Marek Novotny <marek.novotny@marspolar.com> wrote:
> >
> > On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
> >> On Sunday, September 25, 2016 at 4:46:47 PM UTC-6, Marek Novotny wrote:
> >>> -----BEGIN PGP SIGNED MESSAGE-----
> >>> Hash: SHA1
> >>> 
> >>> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
> >>> >
> >>> > On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
> >>> >
> >>> > (snip)
> >>> >
> >>> >> >> This is a test forgery with permission of the email account owner.
> >>> >> >> Steve, I said most all headers can be forged.  Both client and
> >>> >> >> server must allow it.  Here I stripped Path and Xref, and gave
> >>> >> >> it a new message-id and organization.  Path preload is against
> >>> >> >> my TOS, Xref only specifies article number and is meaningless
> >>> >> >> outside that server, Organization because the server adds one
> >>> >> >> if I don't, and of course it needs a unique message id.
> >>> >> > 
> >>> >> > Didn't fool it but the headers aren't exactly the same
> >>> >> 
> >>> >> Could be login/messag-id tracking, but what do you mean
> >>> >> by "didn't fool it"?  Do you mean because it's not a unique
> >>> >> post here:
> >>> >> 
> >>> >> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
> >>> >
> >>> > I think so. I have to login to send a post and when I do 
> >>> > it's say 'me' instead of 'Steve Carroll' so I can spot them 
> >>> > right away.
> >>> >
> >>> >> Would it have made a difference if I had not posted as a followup,
> >>> >> but instead as a new post?
> >>> >
> >>> > I dunno. So is my pgp working when I manually do the
> >>> > line lengths? Or will that string you posted above break?
> >>> 
> >>> Have you uploaded your public to a couple of the big key servers?
> >>
> >> I thought I did. I wish I could get slrn back. I screwed up the .slrnrc
> >> file's replyto line, it was working, then I went to add something that
> >> I probably didn't need to add (port number) and blew that line out. I
> >> thought I've been putting it back in properly but it's not working :(
> >
> > I need a virgin slrnrc file. There should be one in the installation
> > somewhere. Mine has been hacked for the last three years and it about 3x
> > the normal size. I have a ton of re-mapped keys for vim style movement
> > which is starting to get in the way of things like this macro. I think I
> > should go back to a more generic use of slrn.
>  
> I just wrote one from scratch... writing this reply in vim


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

LOL! I couldn't even get reading back, idiotic jackass... I wasn't anywhere near posting yet.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJX6F3kAAoJELnOYK54exUC5IEP/Rar7BC36GSJ87KOG2c0Wm8m
/yIlFcLNCN0m8ZUQr4GfPMWcG3G3e0qYY6CkAvxoWmWPFd9REtsU7IcNN1HED6bi
CzGH0jwIjFeHS3+2jPjaoL68MNRFE5F4Oq21S3hFaLrT5tCnU2Tj14ZoC+Bl92yo
cXLkYnuGFprvdVTra1xnXj5d++8jfe4VJHYX7zvEgxRe3KYLwEWdxkFUsVeUhHZD
bHt6KDpLJRehXwKsPGURFg5RoA/Gm5dLCyLiSgilSGTXXGYmayUctvk6JEbindr9
X6vWk16f9G9yWcfEtosmoiOOl7EpvrC3RU3Ki1m7CxtokMvU7kYwI9OxpG0te28K
/7CW+/7mjOBVq/+m3sUnnpwbYgdaZ5EbD5pQVfJxadfUW/P1asvD90Y0Up0JcMxK
D6k/Xw+TifdY2AU/j1FKEx39qzz0FSxvz+RGM8/zaUkbjf2YANARdJbbl73DUyA3
l1kRkqJvdyZLgLkSyAVlAy5DkgmWGGnZgmas2Rqu2KaklyN20XyS8ZmXUwWkivl5
rQmP4ZgezZVQ59KGK/AvzJrMCFUh93pEF2Ap+NUtkfUcVH0CLuG8vvwf3CA3usdY
XzsHcwJcoWANDMgKSlFpqiZLbMefe7ISgqxpLqvsY+oxWQD78a4k67Cc/C+hHHzC
n0x02D10I2KSc4A/KJin
=ivmN
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#372813

FromMarek Novotny <marek.novotny@marspolar.com>
Date2016-09-25 23:47 +0000
Message-ID<UNKdnRmiV7uB_3XKnZ2dnUU7-S-dnZ2d@giganews.com>
In reply to#372811
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2016-09-25, Steven Petruzzellis <OLnewscat3three@news.eternal-september.org> wrote:
> On 2016-09-25, Marek Novotny <marek.novotny@marspolar.com> wrote:
>>
>> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>>> On Sunday, September 25, 2016 at 4:46:47 PM UTC-6, Marek Novotny wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>> 
>>>> On 2016-09-25, Steve Carroll <fretwizzer@gmail.com> wrote:
>>>> >
>>>> > On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
>>>> >
>>>> > (snip)
>>>> >
>>>> >> >> This is a test forgery with permission of the email account owner.
>>>> >> >> Steve, I said most all headers can be forged.  Both client and
>>>> >> >> server must allow it.  Here I stripped Path and Xref, and gave
>>>> >> >> it a new message-id and organization.  Path preload is against
>>>> >> >> my TOS, Xref only specifies article number and is meaningless
>>>> >> >> outside that server, Organization because the server adds one
>>>> >> >> if I don't, and of course it needs a unique message id.
>>>> >> > 
>>>> >> > Didn't fool it but the headers aren't exactly the same
>>>> >> 
>>>> >> Could be login/messag-id tracking, but what do you mean
>>>> >> by "didn't fool it"?  Do you mean because it's not a unique
>>>> >> post here:
>>>> >> 
>>>> >> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
>>>> >
>>>> > I think so. I have to login to send a post and when I do 
>>>> > it's say 'me' instead of 'Steve Carroll' so I can spot them 
>>>> > right away.
>>>> >
>>>> >> Would it have made a difference if I had not posted as a followup,
>>>> >> but instead as a new post?
>>>> >
>>>> > I dunno. So is my pgp working when I manually do the
>>>> > line lengths? Or will that string you posted above break?
>>>> 
>>>> Have you uploaded your public to a couple of the big key servers?
>>>
>>> I thought I did. I wish I could get slrn back. I screwed up the .slrnrc
>>> file's replyto line, it was working, then I went to add something that
>>> I probably didn't need to add (port number) and blew that line out. I
>>> thought I've been putting it back in properly but it's not working :(
>>
>> I need a virgin slrnrc file. There should be one in the installation
>> somewhere. Mine has been hacked for the last three years and it about 3x
>> the normal size. I have a ton of re-mapped keys for vim style movement
>> which is starting to get in the way of things like this macro. I think I
>> should go back to a more generic use of slrn.
>  
> I just wrote one from scratch... writing this reply in vim

Indeed you are. Do you have a command line gpg?? 

- -- 
Marek Novotny
- -----------------------------------
email: marek.novotny@marspolar.com 
  Git: https://github.com/marek-novotny
GnuPG: https://www.dropbox.com/s/ey9h0bovmok5ph8/marek.novotny_pub.asc?dl=0

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJX6GIYAAoJEC9nkebvym+h0U0P/2Z8e3TB+WZLg9Jmj2iunCev
ymZHdyzie9OH2TeIUkizpwgqhnzRYZfnPf1UKOTD1fOsOI6h767D9d3smZCior2T
xUI/49X+uR+0+e3YXMdsmOiR+0f1Cfj8zchm59Mbs1PzHlfSJFbxz0ds181qxdRl
OnH+WSdeO0Rk+a4PN1KeswWXLa1gB+E0u1bL2MqLrgArdyDHAvkNisfRJLn7tkmM
tqn0NhTdBi6pkjwX1Zfde1A20Rq+a3h2nJ1qaRCRO1S1RMDhNR4HGRH1Y6pI8+1R
3cMHlHQRXxm+iO4lE35iIMyAzss5wKqE9+N3YOLoU43gBpMTk/olkVxsnjfz7WYW
eKZIyzPnyA7ysNqOduvsyyWiJ0SJBGlsZJn1AN5inng2sYJbIBNjpMoAhwrpNsoy
XUG8Xi0pUSTbQAekkZoYFHYXR2DvucBuSsnhepQwZ4NxzQj0KP0sFcUsbnEnSd2x
Y6F+2SwR9gcYPVB16dp6nUA7YMhqmY1QU/h4KwzhTHm6ZPUDMk+1zNj/Sto/qyRR
sfPoEUle1k/csSllS/OH4bYm/qscOW5AuQwqp66fMVyrSIWy48s0nGZvQe36BghH
+qNlPXqUwALakWrago9FPOMhmFWE1KQNyv7+A5TVxJlD2k3NA+MTLzVmxGoAh+aS
ygL90DYTn+xoWJeTw7Fr
=tJRd
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#372808

From"Octavian W. Lagrange" <olagrang@perch.invalid>
Date2016-09-25 23:10 +0000
Message-ID<hjfadgud9d.ko@perch.invalid>
In reply to#372798
Steve Carroll <fretwizzer@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> On Sunday, September 25, 2016 at 4:29:00 PM UTC-6, Octavian W. Lagrange wrote:
> 
> (snip)
> 
>> >> This is a test forgery with permission of the email account owner.
>> >> Steve, I said most all headers can be forged.  Both client and
>> >> server must allow it.  Here I stripped Path and Xref, and gave
>> >> it a new message-id and organization.  Path preload is against
>> >> my TOS, Xref only specifies article number and is meaningless
>> >> outside that server, Organization because the server adds one
>> >> if I don't, and of course it needs a unique message id.
>> > 
>> > Didn't fool it but the headers aren't exactly the same
>> 
>> Could be login/messag-id tracking, but what do you mean
>> by "didn't fool it"?  Do you mean because it's not a unique
>> post here:
>> 
>> https://groups.google.com/forum/#!profile/comp.os.linux.advocacy/APn2wQex7ZDHcyvKXrYEFomvvGEe6q-7LlNoING2TTevZvRIYzflnEJjf7Vl4bCLnGnc9SiNpURO
> 
> I think so. I have to login to send a post and when I do 
> it's say 'me' instead of 'Steve Carroll' so I can spot them 
> right away.
> 
>> Would it have made a difference if I had not posted as a followup,
>> but instead as a new post?
> 
> I dunno. So is my pgp working when I manually do the
> line lengths? Or will that string you posted above break?
> -----BEGIN PGP SIGNATURE-----
> Comment: GPGTools - https://gpgtools.org
> 
> iQIcBAEBCgAGBQJX6FNVAAoJELnOYK54exUC4/YQALM1sG2QFZuRAgoqSLSoq2W0
> WPJ7B5bt+V8hWwohz6Q351qD7s5TUnqumrQ/Eif6tqLE6wYP41vRXmfrTP9mFCAi
> BTT9q9BL/xAIObPSHJjfIBjhLu5s/SeTBcLZMupQcPmtFX8nU4ji/4joRnY0aVcr
> bHw8crl5jsx/zUkg6SmKbm2USpRTUAF9evNhB3UhOjjsQ/nfhfEU2Puf1Sy8WWbI
> 2nc1fTudlcAP7l3o7izoQJdIwB8Gzdt2T6ArFHBH9T0NWrukkIT6l7w5ai6dviqM
> 0S3WhHh5mYhyajRfEZzMgTsNQUhaldmmCDSCamiv4GyFCSo4lq3gbXRivEZwk5xL
> 1Oxpyo+20Vc3P6jfW905MVS+RyzaSH3zGAx1VMmnjSwaJJAbxNMD+fpuKimpFEQG
> dhEl65n4ISa1iN1pRbPFRZOqMt+75wyfHUzs96WUvLitiMMvwN94yjvAV0mpWiz1
> l49FEaHU5akupoTFLTDW4WNK10Ai4mEzkCm9pxOL8wwXJTc04ZKytjLs+tS7mvA3
> 3E/BFcSRieqqC8r8ELZq6p23tRIqbSdieQhDxuJsp7BOHeNMgaIrJoc7JjAV4r2C
> zbPBWlFYDGzXRCHMzlsFcZ7v+Y0rYgFHxjSdFvhRNX2pwEmYKDGTK2C/fMAUntZF
> YYfQCwyj55Rj8NvhOUGr
> =H6w8
> -----END PGP SIGNATURE-----
> 

Good sig on this post.  That wrap is ok.

[toc] | [prev] | [standalone]

Back to top | Article view | comp.os.linux.advocacy

csiph-web