Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.privacy.anon-server > #66414
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Newsgroups | alt.privacy.anon-server, alt.os.linux, comp.os.linux.misc, alt.comp.os.windows-10 |
| Subject | Re: Good example why business emails should be PGP'ed |
| Date | 2018-09-27 20:07 +0000 |
| Organization | NOYB |
| Message-ID | <pojkai.ar4.1@ID-201911.user.individual.net> (permalink) |
| References | (7 earlier) <g14ar9Ffdg9U1@mid.individual.net> <270920181152348031%nospam@nospam.invalid> <g14dmrFg12cU1@mid.individual.net> <270920181215330809%nospam@nospam.invalid> <g14lv6FhnobU1@mid.individual.net> |
Cross-posted to 4 groups.
Carlos E. R. <robin_listas@es.invalid> wrote: > On 27/09/2018 12.15, nospam wrote: > > In article <g14dmrFg12cU1@mid.individual.net>, Carlos E. R. > > <robin_listas@es.invalid> wrote: > > > >>>>>>>>>> People with which I needed to use encryption were unable to set any > >>>>>>>>>> encryption method up. A lawyer, for instance. I would have to go to > >>>>>>>>>> his > >>>>>>>>>> office and teach him. > >>>>>>>>> > >>>>>>>>> use an encrypted email service. there's nothing to set up. all they > >>>>>>>>> need is a browser or an app on their phone. > >>>>>>>> > >>>>>>>> That would require a binding contract and spend money, which they did > >>>>>>>> not want to do. > >>>>>>> > >>>>>>> no it wouldn't. it only needs a mutual agreement to use an encrypted > >>>>>>> medium. there are free options as well as paid ones. choose whichever > >>>>>>> one works best for all parties involved. > >>>>>> > >>>>>> Not for a lawyer, it wouldn't. He would be directly liable if the email > >>>>>> gets intercepted or somehow compromised. > >>>>> > >>>>> it's actually ideal for a lawyer, since it's basically impossible to > >>>>> intercept and crack end-to-end encrypted email unless the passcode is > >>>>> something trivially guessed. > >>>> > >>>> We know that. He may or may not, but that would be irrelevant. :-) > >>>> > >>>> He needs to pay someone that says "yes, this is safe". With a contract. > >>> > >>> not if he uses a free service that states that, which i said exist. > >> > >> Not valid enough for the lawyer. He needs someone to sue. > > > > not for every item he uses. > > Something as crucial as mail? Certainly. Ask them... I don't know about you, but I found this part quite funny, not to say hilarious: > >>>> He needs to pay someone that says "yes, this is safe". With a contract. > >>> > >>> not if he uses a free service that states that, which i said exist. A *lawyer*, trusting a *free* service saying "yes, this is safe"!? nospam at his best!
Back to alt.privacy.anon-server | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Good example why business emails should be PGP'ed Fritz Wuehler <fritz@spamexpire-201809.rodent.frell.theremailer.net> - 2018-09-23 19:45 +0000
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-23 22:03 -0400
Re: Good example why business emails should be PGP'ed Dan Purgert <dan@djph.net> - 2018-09-24 10:27 +0000
Re: Good example why business emails should be PGP'ed anon <noreply@mixnym.net> - 2018-09-24 07:48 -0500
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-24 13:18 -0400
Re: Good example why business emails should be PGP'ed anon <noreply@mixnym.net> - 2018-09-25 08:16 -0500
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-25 10:26 -0400
Re: Good example why business emails should be PGP'ed Wouter Verhelst <w@uter.be> - 2018-09-25 17:17 +0200
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-26 14:16 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-26 14:24 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-26 14:47 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-26 14:56 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-26 22:20 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-27 00:43 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-27 11:21 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-27 11:52 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-27 12:10 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-27 12:15 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-27 14:31 -0400
Re: Good example why business emails should be PGP'ed Frank Slootweg <this@ddress.is.invalid> - 2018-09-27 20:07 +0000
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-27 16:39 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-28 09:45 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-28 09:52 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-28 14:22 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-28 14:26 -0400
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-28 15:43 -0400
Re: Good example why business emails should be PGP'ed nospam <nospam@nospam.invalid> - 2018-09-28 15:54 -0400
Re: Good example why business emails should be PGP'ed The Natural Philosopher <tnp@invalid.invalid> - 2018-09-27 06:52 +0100
Re: Good example why business emails should be PGP'ed "Carlos E. R." <robin_listas@es.invalid> - 2018-09-27 11:22 -0400
csiph-web