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

Groups > comp.os.linux.advocacy > #373535

Re: ping Marek

From "Octavian W. Lagrange" <olagrang@perch.invalid>
Newsgroups comp.os.linux.advocacy
Subject Re: ping Marek
Date 2016-09-30 02:13 +0000
Organization O.W.L.
Message-ID <ahgjafi9f.ae@perch.invalid> (permalink)
References (4 earlier) <f276c827-dfb8-4c63-87d1-03d988da5975@googlegroups.com> <nsk8ks$1k4$2@dont-email.me> <e55n6hFp9ndU1@mid.individual.net> <hajgde9.jafi8@perch.invalid> <e55uc8FqnbfU1@mid.individual.net>

Show all headers | View raw

Jim Polaski <jpolaski@linuxmail.org> wrote:
> On 2016-09-30, Octavian W. Lagrange <olagrang@perch.invalid> wrote:
>> Jim Polaski <jpolaski@linuxmail.org> wrote:
>>> On 2016-09-29, Silver Slimer <> wrote:
>>>>
>>>> On 2016-09-29 7:24 PM, Steve Carroll wrote:
>>>>> On Thursday, September 29, 2016 at 5:04:02 PM UTC-6, Steve Carroll
>>>>> wrote:
>>>>>> On Thursday, September 29, 2016 at 4:59:39 PM UTC-6, Octavian W.
>>>>>> Lagrange wrote:
>>>>>>> Steve Carroll <fretwizzer@gmail.com> wrote:
>>>>>>>> On Thursday, September 29, 2016 at 3:24:09 PM UTC-6, Octavian
>>>>>>>> W. Lagrange wrote:
>>>>>>>>> -----BEGIN PGP MESSAGE-----
>>>>>>> ...
>>>>>>>>> -----END PGP MESSAGE-----
>>>>>>>> 
>>>>>>>> 
>>>>>>>> What app is that?
>>>>>>> 
>>>>>>> tin/vim.
>>>>>> 
>>>>>> -----BEGIN PGP MESSAGE----- Comment: GPGTools -
>>>>>> https://gpgtools.org
>>>>>> 
>>>>>> hQIMA+W+Ippu/VtHAQ//SuvN0ZNgxVIHr3gZUG1iyqIGR8zqys2Dmn1dWoEr/q95 
>>>>>> 9GaFxu2BMm2TB7ZA+dYR21c5nNrhD5S24J2VuHsCUwLaGx443aS9r3x71o6iXYB9 
>>>>>> ue4TUPrWyDKSu8oEGAXfIk3vrjH5pXNHE2hxByrh3bLy668R0cgoUcS/F2yZJAQ2 
>>>>>> GFt2udLYFP29ZSmIexXebpskEl+QF9xOR+HDnh6B9/RR1k+bYBoBEKW5LFALzp5/ 
>>>>>> CLFYtovuXSQqicTWahlPc7+7csh+WrxNVK3gylWSXOkKnnX1mifn7ZR8QvMvrGqW 
>>>>>> 9ZoGWmXBFH9NBUQFSO7VK9QYQ25JZnGCSgqHyQoP/ErRs31yu85o1a7JoE3EEpbe 
>>>>>> tfovqXiYJU+CNN1zmswwt5IVZXF9MbuSMOHfmz0Cj2/zoN8ysqT/aWsDAS3lgIVm 
>>>>>> updMxgmSxMZb3oJAvXFr0I4Oo8AC3Zjn7Yhr7L9wA116WNrWtrxjl97s7Yssnbcj 
>>>>>> riFvRKaYT/UBK9F+puuDMb77riJuO7pGl4Ksbe+StTG9KWqZTdv5dj3KhiX3WSgQ 
>>>>>> GDNRlrnHjePd0Vr0IaSuXTngNLCK8X6B+CPw0f8pwJax6JtpkQA8wirsgxH+xXnA 
>>>>>> UPeBOz0a3xltMaXFvdBOKriy0ev0CVWgS3BIyByouD6mpQWGR6xy9v70Aim4W66F 
>>>>>> AQwDZuuZanuRsAoBCACt9sZmxp92fPwjq8VkGvroID80ke9pVOY6c/NrakvBIa5X 
>>>>>> JYdCAV9RM7q/Dv4VoY7JuFaozdxecMdrtcq31fcFKxB5JXB1A/gOSsNyR0g5J1ke 
>>>>>> rh/cj4B0ih7pUVTYdtqGw7Z0I3ql525bbEfimwfjAT6HzCX/ju1eFXomURFafgUP 
>>>>>> YLVHJu4v+sCazI9MqEb9j2RZEImPgTL1+xsYiPvMLxjOkO5UHNICoUKPjKgmtto7 
>>>>>> Ia3bLLymeaoXo8Mu/oBANpeF5a9xPqq/GVUfUBcJgumQK4QuPUl/s8mBgecGa0X7 
>>>>>> Vba6n2HRzX+rMex1aSeJDCyTiHiS+YfjvYa0/Lfc0l0BDLEiSDwz9obmaHetv3yG 
>>>>>> mG/G6I5G+8fsF2uNasysHxWB8RE2jtKIB0O4Or9rVJq5YTv9i11DF+YfzIV+KoQM 
>>>>>> 2juynuzljRvJxwdavyMKovnxapLILFbcy1VJyd0= =OISj -----END PGP
>>>>>> MESSAGE-----
>>>>> 
>>>>> What gives? I can read yours but no one else's.
>>>>
>>>> People have to be careful when posting an encrypted message to
>>>> actually select who they want to have reading it. It's cumbersome, but
>>>> look at it this way: if, in the future, we want to post to the whole
>>>> newsgroup and want everyone but the Prescott Parasite to be able to
>>>> read it, we'll be able to simply omit checking his name and he'll only
>>>> see the same kind of gibberish as what you just quoted.
>>>>
>>>>
>>>> - -- 
>>>> Silver Slimer
>>>> Islam is a disease
>>> 
>>> IMHO you guys are shooting each other in the foot.
>>> Most people are just going to move on without reading it.
>>> 
>>
>> It's fairly transparent with something like thunderbird/enigmail.
> 
> I must be missing something. Stick with me on this one. 
> 
> 1. You guys create a public key, load it up to a server somewhere.
> 2. People see your message with all the key hex stuff in it.
> 3. What now?
> 
> I see several types of messages here in COLA.
> 
> 1. Message with the key at the end.
> 2. Message with no key
> 3. Message that is nothing but a key. 
> 
> So for 1 and 2, I can read them fine. One look at the email or header 
> and I know if it's the real person based on what I know about that 
> person.
> 
> What is 3?
> Is that just you guys sharing the key?
> Or is this something that is completely encrypted that cannot be read 
> without the key?
> 

Directly below is my gpg public key.  You would import this into
your gpg keyring.  To send an encrypted message to me, you would
just encrypt that message to my public key.  To decrypt a message
that is encrypted to my public key, you have to have my private
key.  Only I have that.  You can however, encrypt to multiple
keys, which is what we are doing.  We define a group in gpg.conf,
then encrypt to the group (it's basically a shorthand way of
listing multiple recipients on the command line).  Everybody
whose key is listed can read the encrypted message.

My public key (betwen beginning and end of PUBLIC KEY BLOCK):

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1

mQENBFU9kmIBCADTeFbOx8j58tMTQauKk5Pk2MR7MgX119siWrNaktnpBGzQofzr
nKuqSYi+34AblPH+UF0678y8cJqqf3AWYmPfk6QxKbNQjfebHboqc9WiZjzTP2vM
5lkc095sG+ZYxEIzLu9ydOVqd1GTpZ0ddqoKRhAt9V2iGrvJrOdFFOFGwSIcH1ZS
gulmlksoBMt60W5gUft9+CK0uoa01AhwjhirxL+wYHAZvwm9oE8AGZfidfVHBt5d
QwMx10e+4KEN+RDJkcSiTuE11UNYMYV8/vqtk9N04l6Zb8xQmLZMNGtQD10cBIQJ
9aFiPMpJ5X1TCk2rSrQ8yYR7I4oy6SyrOGyLABEBAAG0Im93bCAodXNlbmV0KSA8
b3dsQHJvb2Z0b3AuaW52YWxpZD6JATgEEwECACIFAlU9kmICGwMGCwkIBwMCBhUI
AgkKCwQWAgMBAh4BAheAAAoJEPmLqQ2wmEqrY7sH/RmmrvaCwlymhVHugZvpUDwX
3TCTf5LQvW6HErxjWgsAT7zpbndhnr1O0kLyD+qdEhakNg8GN19fLqjd2lobj/sk
FVNRgi1aLaCxjJcTa+wBsHPspBSDxPP52X8VAVVgnS+e34Fubb1kPFijBkcKOR1i
TSmcHQ+C5P6IXaV7g/6WmbvBYqfmvxOtMZ+SfffUKH5n84cZkHAT4DvZQ7v5EgfX
FTh5mIkk2t7K74JUxUaC/cM0gZUvYzp50H3Q0ldfzBcOTujDek9/3bs5nPcWXr7L
OXOvkDLI9v8JCRrP3wGSAF9nIkes0NdrEResEmQCsWo8UVNoccsYCZpNbWHMOM25
AQ0EVT2SYgEIAMZZJIzCO1GAgjt2c33yvjMAl1/ZbitU9lc+lR6UaXNQi7PMdS6j
SNKiouCIyZnx5kVrJRmTX6Qq+7BMhDspqV3Qz+t76ThUcAdYbt95BNNdScYI4gia
CVa66FA3Ryw0x2jWDvomcLuyJ5BNWrz7/AoGS3e1nDAzk4F6Doe0vg46i5naNflq
M93XEVjV+5h8iOZMyOP2+TrjSS3cNZRu6egqI3t4YdXvL7RjLQKz8yGH1tavuPrZ
+eKtltbQ5QOZw1OxnS57xv1giNfRhjMqugyiSlo9n5qdytbNQ5n/dLk3PTEw+9ak
+CqADTBtlQWrzDD8hB+GbbiTNopCG2j3IhUAEQEAAYkBHwQYAQIACQUCVT2SYgIb
DAAKCRD5i6kNsJhKqwYICACVlMkQHk7s61X7oxCeQp3I5zyqMx6gl14SyfKMLmva
Pr6V8d2dhSMPk1EFyquMRthhAbQiX1PZyKwx9ce2OvVWZ602j6RQrwIaPFGulw0W
GYoxCbfOvMRou9B/O9SlQb22scncfHMIs0oha/buwepX3S93CDpjvpZ/C4xd3J45
R0kv2aQ5FBWJj0Fq3ho36aHTFDDOwhlNScbQoOPZ300Ss1ZDTvJn1plqwdzr1MYl
ZJ/7eV8jUvuQrij0lkoXL6hJD6JIfU2aM2e8UI4EJbdIhS+ctfM0Kzew60jPbwjS
EXVG8IUSRVGGQZkD7v0TMiMLMEevIYZBWqOOSvV0vLxh
=BKjR
-----END PGP PUBLIC KEY BLOCK-----


Below is an example (partial) of an encrypted message
(between begin and end of PGP MESSAGE):

-----BEGIN PGP MESSAGE-----
Version: GnuPG v1

hQEMA88pYYPQO0xFAQf/e7zfhl3DUmfcMZI9kF1L+3xBCmiLsldDpQJqmKi96aJs
sO4OELHvkPUPKFzPh+M5h3lJ1P70TxSmd2cYVp+hEVlwYE+YmzZZDQSXaadlMKmx
SCXdR49EO+WrSZRQv5qLl6SJTdkD9mwLS+s5a/7WUd1Pv8m+qcFAGVvnZOOvJIlQ
X5m3G8rlsXM7C9uZoFY94YIu3cn4u/eyvwh7TyvhGVV1Tu1YHxdQjx18FtU9YgwW

...

nmvgV2BdjG6MB8ImgCNo/BuT1WVq7l7oM9VJ5O/5cD2npLzgMGKTql7wQ00k9OAR
iJY2DVwP7Om0H0y1B0rSE+ruUNSOsnPixmHUmcueOoHZDSWa134cnRHdh0ZxXmRD
4cXswAt22WHDQ2AsKSgMwXgaX0GwlgCvkteTqvE+97YFvxyGztySBtfw1lokkVZh
byRhjIPlB6ZXhCeWXuJ9+IpQ1nT1xVtGbjo33sljsawWP4xBbC31IM42rxGtNrMQ
4ej9Nq52sEWpQ9z5iogsOvgfByms0Vj0ldHnlfBsf9cuYN84RN/hjcGgR8R0Cp03
7SyUT2P55Y+eNdC4ZE5W7QyfAGK1MTgcU8Z5TEby2wSZ
=ntfx
-----END PGP MESSAGE-----


Below is an example of a signed plaintext message, where the
sender can be verified (but you could both sign and encrypt):

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This was written by me.  The sig proves it.

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

iQEcBAEBAgAGBQJX7cYNAAoJEPmLqQ2wmEqrG70H/jrIMHlwWTbH6V/CIQSQQri9
PMvBmvTx3qU5IsCK/KilCdYRO0uS4hdkQrc0VysBNgRR6avVj3jpMwcmjwRxuPD+
2YLA2YMkl8hYFLH+56ugLNdDfjRxIad7nJZ5IcEqZzQYBpVB70CMirJxG0vhmqA5
Yf3Nt/uzmo8rerm3O/I95ZP3VUd7fJ8Mzz1KvcZe/CiynDF3vSBxlz5kuHIUHyHd
je+2IJYrAuJnaZbpJ6Bb4nsKBOVTHsnVauAWQMYcm7zIYiFaznjZ6I4tgV2TL9XE
yo92QuVk4seVaINFbjQhkh+uNl6K4vjpFyUZNS6/h+aBfo0oSUUne9coTkrqldY=
=14h9
-----END PGP SIGNATURE-----



> 
> 
>>> The way to eliminate the Prescott Parasite is to completely ignore him.
>>> Talk about him but not directly to him. It's obvious he is showing the 
>>> early signs of a breakdown already. The side benefit is we all get to 
>>> watch him implode. 
>>
>> This has the same effect and also slams the door in his face.  He's
>> starting to climb the walls already.  It would be interesting to see
>> how things turned out if everybody participated.  Get gpg and post
>> a public key.  DFS is skeerd for some reason. 
> 
> I'm gonna try it, but be warned I know less than zero about this so I'm 
> going to screw it up and ask for help digging myself out of my own mess.
> 

No problem.

> The Prescott Parasite is indeed climbing the walls.
> No question about it. His latest Star Trek Rainman act is quite odd 
> indeed.

Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-29 21:24 +0000
  Re: ping Marek Marek Novotny <marek.novotny@marspolar.com> - 2016-09-29 21:29 +0000
  Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 15:44 -0700
    Re: ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-29 22:59 +0000
      Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 16:03 -0700
        Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 16:24 -0700
          Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-29 19:38 -0400
            Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 16:40 -0700
              Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 07:47 -0400
                Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-30 08:49 -0700
                Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-30 09:13 -0700
                Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 12:16 -0400
            Re: ping Marek Jim Polaski <jpolaski@linuxmail.org> - 2016-09-29 23:42 +0000
              Re: ping Marek Snit <usenet@gallopinginsanity.com> - 2016-09-29 17:27 -0700
              Re: ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 01:14 +0000
                Re: ping Marek Jim Polaski <jpolaski@linuxmail.org> - 2016-09-30 01:44 +0000
                Re: ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 02:13 +0000
                Re: ping Marek Marek Novotny <marek.novotny@marspolar.com> - 2016-09-30 02:22 +0000
                Re: ping Marek Jim Polaski <jpolaski@linuxmail.org> - 2016-09-30 03:44 +0000
                Re: ping Marek Snit <usenet@gallopinginsanity.com> - 2016-09-29 21:40 -0700
                Re: ping Marek Snit <usenet@gallopinginsanity.com> - 2016-09-29 19:12 -0700
                Re: ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 03:17 +0000
                Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 08:05 -0400
                Re: ping Marek Snit <usenet@gallopinginsanity.com> - 2016-09-29 18:33 -0700
              Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 07:49 -0400
            Re: ping Marek Snit <usenet@gallopinginsanity.com> - 2016-09-29 17:48 -0700
          Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 16:41 -0700
            Re: ping Marek "Octavian W. Lagrange" <olagrang@perch.invalid> - 2016-09-30 00:47 +0000
              Re: ping Marek Steve Carroll <fretwizzer@gmail.com> - 2016-09-29 19:08 -0700
                Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 08:06 -0400
            Re: ping Marek Marek Novotny <marek.novotny@marspolar.com> - 2016-09-30 00:51 +0000
            Re: ping Marek Silver Slimer <.m@nsn.s> - 2016-09-30 07:48 -0400

csiph-web