Text 25940, 106 rader
Skriven 2006-02-25 23:15:00 av Dale Shipp (1:261/1466.0)
  Kommentar till text 25928 av Michiel Van Der Vlist (2:280/5555)
Ärende: Re: Elist mergers
=========================
 -=> On 02-25-06  10:46,  Michiel Van Der Vlist <=-
  -=> spoke to Dale Shipp about Elist mergers <=-

 MVDV>> We don't really know if they all made a free choice do we?

 >    They had multiple choices -- they could have sent their

 MVDV> But only one of those choices - sending it to Thom - would
 MVDV> have satisfied the requirement that it must be listed in
 MVDV> the Z1 e-list in order to be carried by the Z1 backbone.

  Not true.  When they initially sent their updates to Thom, he was one
  of several who had offered to keep an Elist that moderators in Z1
  could easily use.   As you said later in your message, his list was
  not "the" Elist in Z1 until after the moderators selected him by the
  fact that many of them send in their listings to him.  They could have
  chosen Peter, or they could have chosen any of several others besides
  Thom who were also in Z1.

 >   If you are talking about the Elist that Thom maintains, then
 > you could have gotten the information which was correct as of
 > the day you wanted it.

 MVDV> Had I been aware of it, yes. You are missing the point
 MVDV> however: the point being that the list I was using was
 MVDV> useless because the information was outdated by up to a
 MVDV> month.

   And so you put the blame for that onto the Elist that Thom maintains?
   I put the blame on your not knowing how to get what you wanted when
   it was readily available.

 MVDV>> My point is that there are many solutions for the cost problem, But
 MVDV>> you do  not want to hear it, you find excuses for rejection.


  There were many solutions.  However, as you often do, we chose the
    simplest.

 >    I am not looking for excuses.  I gave you the reasons that
 > existed back then.

 MVDV> Which I think were excuse. There were alternatives and I
 MVDV> gave you some which would not have involved any extra cost.
 MVDV> But you reject all except the one that involves a Z1 e-list
 MVDV> keeper.

  It was the simplest.

 >>>  Never mind, telling me how you would encrypt it in a manner that
 >>> would allow me to decrypt it.

 MVDV> I never trust people who say "trust me".

  Or "I'm from the government and I'm here to help you."!

 >>    So tell us all how you would set it up.  Don't duck the question.

 MVDV>> I am not going to write a tutorial on PGP. That would be

 >    Don't need a tutorial on PGP.  Send me your PGP key and
 > I'll try to see if my uplink will accept an encrypted netmail
  > for you. You can use netmail or you can use the email address below.

 MVDV> You should have my key by now.

   I do.  We'll eventually see if my encrypted response to you gets
   passed or blocked by whatever route is used to get netmail to you and
   if you can decrypt it.  It remains to be proven that we can each
   trust the keys that we will have exchanged.  That is one of the
   problems with PGP.

 MVDV>> reinventing the wheel. The information is freely available
 MVDV>> at various places. PGP is freeware. I can make it
 MVDV>> requestable from my system too if you want.

 >   No need.  I've had it on my home computers for years, and
 > known about and understood the algorithms it uses for decades.

 MVDV> So your were just kicking up dust and trying  to get me to
 MVDV> do some needless work when you challenged me to explain how
 MVDV> a message should be encrypted. Good to know you employ such
 MVDV> tactics.

  I never said that I did not know how to establish secure
  communications.  I said that it is not easy, and that people who try
  to do it often make very bad mistakes.

  PGP is one way that is reasonable once there is a chain of trust.  It
  is not without possible problems however.

  I've seen many other methods proposed by supposedly knowledgeable
  people that are either not secure or are not reasonable.

                               Dale Shipp
                  fido_261_1466 (at) comcast (dot) net
                              (1:261/1466)




... Shipwrecked on Hesperus in Columbia, Maryland. 22:55:00, 25 Feb 2006
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01
 * Origin: Owl's Anchor (1:261/1466)