Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #109853
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: Backups |
| Date | 2023-11-09 15:22 +0000 |
| Organization | NOYB |
| Message-ID | <uij0vb.18lc.1@ID-201911.user.individual.net> (permalink) |
| References | (9 earlier) <uiibji$25agf$1@dont-email.me> <kr3sioFsdr5U4@mid.individual.net> <uiik9m$26t21$1@dont-email.me> <uiiplg.jd4.1@ID-201911.user.individual.net> <uiioul$27pis$1@dont-email.me> |
Java Jive <java@evij.com.invalid> wrote: > On 09/11/2023 13:17, Frank Slootweg wrote: > > Java Jive <java@evij.com.invalid> wrote: > >> On 09/11/2023 11:02, Carlos E. R. wrote: > >>> On 2023-11-09 11:17, Java Jive wrote: > >>>> On 08/11/2023 14:53, Frank Slootweg wrote: > >>>>> > >>>>> Java Jive <java@evij.com.invalid> wrote: > >>>>>> > >>>>>> On 07/11/2023 20:26, Carlos E. R. wrote: > >>>>>>> > >>>>>>> Oh, I did reply. You are not ilustrate enough to understand. > > [...] > >>>>> Anyway, before criticizing others, first learn the difference between > >>>>> end-to-end-encryption and no encryption. That Joerg is siding with you, > >>>>> should be a red flag, a *big* one! > >>>> > >>>> No-one has answered my basic point that, if Google run the OS, and > >>>> Carlos can read the message, so can Google, > > > > No they can't. See below. > > > >>>> and, given Google's track > >>>> record, most probably they will. > > > > You're still misunderstanding/misrepresenting "Google's track record". > > Footstamping doesn't make a credible argument. > > Track record is all anyone has to judge a company. I can only suggest > that you read Shoshana Zuboff's book "The Age Of Surveillance > Capitalism" which goes into detail on their track record. Irrelevant. You misrepresent what Google is doing with Gmail and you misunderstand how E2EE works / does not work. > >>> Yes, we did. > >> > >> No, you didn't ... > >> > >>> Google can not read the messages, that's the whole point of E2EE. > >> > >> ... because Google is running the OS that is decrypting it for you. > > > > Nope, the OS is not doing the decrypting. > > > > But your -invalid - point seems to be that someone - i.e. also Google > > - could have a backdoor somewhere. > > > > Yes, that's theoretically possible, but in practice it's extremely > > unlikely, because that would get them in big, big trouble. > > No back-doors are needed when the front is wide-open. The results of > decryption are fed back through the OS to be given to the user. Nope. That's not how E2EE works. The OS does not see the decrypted data (unless there's a backdoor). Example: WhatsApp and other IM platforms. > > But even if you accept that premise, it also holds for any other > > company which provides end-to-end-encryption, so you haven't any real > > argument whatsoever. > > > > So let's turn this around: What *proof* do *you* have that some other > > company can *not* read your end-to-en-encrypted messages? > > This argument is exactly about Google, so why try to omit them from the > argument? I don't omit them, you single them out. > The point of principle is that *any* company, *including* > Google, that provides an OS can read the results of a decryption after > it has taken place within that OS, But that's your false premise, the decryption does *not* "take place within that OS". > so all the general public have to go > on in deciding whether to trust such a company is track-record, and > Google's does not encourage such trust. Well, on *this* (note emphasis) aspect (RCS E2EE), I trust Google more than some Usenet poster who 'compares' totally different subject matters. I'm done. 'End-to-end encryption' <https://en.wikipedia.org/wiki/End-to-end_encryption>
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-02 20:23 +0000
Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-02 21:06 +0000
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:50 -0400
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-02 17:29 -0400
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:34 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 06:38 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-03 08:27 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-03 10:13 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 08:46 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 10:01 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-04 10:44 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:53 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 11:54 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 14:43 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-04 16:13 +0100
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:30 -0400
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-05 14:24 +0000
Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-06 00:44 +0900
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-05 18:25 +0100
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 15:57 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:53 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 11:25 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-06 14:43 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:28 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:30 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-07 15:15 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:24 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:29 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 17:35 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:43 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 19:57 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 21:38 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-06 21:08 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 22:14 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-07 21:26 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-07 21:35 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-07 20:49 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 14:53 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 16:12 +0100
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-08 16:33 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-08 19:54 +0100
Re: Backups Kenan ÇOT <kenancot34@gmail.com> - 2023-11-08 11:18 -0800
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 10:17 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 12:02 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 12:45 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 13:17 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 14:05 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 15:22 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:09 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-09 19:04 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 20:44 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 21:49 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:35 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 23:21 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 00:06 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:08 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:44 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 20:10 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 21:26 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 23:09 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 23:00 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-11 00:20 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-11 12:55 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:29 +0000
Re: Backups Jim Jackson <jj@franjam.org.uk> - 2023-11-14 13:04 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-14 15:44 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 15:24 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 13:51 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:40 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-10 18:55 +0000
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 22:20 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-11 14:59 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 20:44 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 21:17 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 22:38 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 23:41 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-10 15:06 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-10 14:45 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-09 15:22 +0100
Re: Backups Java Jive <java@evij.com.invalid> - 2023-11-09 17:11 +0000
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:19 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:18 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 01:54 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 17:21 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 18:33 +0100
Re: Backups Jörg Lorenz <hugybear@gmx.net> - 2023-11-06 19:06 +0100
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-06 19:13 +0100
Re: Backups Ed Cryer <ed@somewhere.in.the.uk> - 2023-11-06 18:49 +0000
Re: Backups Larry Wolff <larrywolff@larrywolff.net> - 2023-11-25 09:35 -0500
Re: Backups Joerg Lorenz <hugybear@gmx.net> - 2023-11-25 16:51 +0100
Re: Backups Arno Welzel <usenet@arnowelzel.de> - 2023-12-04 20:44 +0100
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 21:29 -0400
Re: Backups Jeff Layman <Jeff@invalid.invalid> - 2023-11-05 16:03 +0000
Re: Backups AJL <noemail@none.com> - 2023-11-03 09:01 -0700
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 13:31 +0000
Re: Backups Adrian <bulleid@ku.gro.lioff> - 2023-11-03 14:25 +0000
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 14:38 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:38 +0000
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:34 +0000
Re: Backups "Carlos E. R." <robin_listas@es.invalid> - 2023-11-04 02:52 +0100
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:39 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-03 16:43 +0000
Re: Backups Theo <theom+news@chiark.greenend.org.uk> - 2023-11-03 21:42 +0000
Re: Backups Dave Royal<dave@dave123royal.com> - 2023-11-03 22:53 +0000
Re: Backups Frank Slootweg <this@ddress.is.invalid> - 2023-11-04 11:05 +0000
Re: Backups Wally J <walterjones@invalid.nospam> - 2023-11-04 14:24 -0400
Re: Backups Andy Burns <usenet@andyburns.uk> - 2023-11-03 17:36 +0000
csiph-web