Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.mobile.android > #154234
| From | "Carlos E. R." <robin_listas@es.invalid> |
|---|---|
| Newsgroups | comp.mobile.android |
| Subject | Re: SMS spoofing |
| Date | 2026-06-19 12:11 +0200 |
| Message-ID | <n9kiucFidf7U3@mid.individual.net> (permalink) |
| References | (1 earlier) <s3crs4nq1d5n.dlg@v.nguard.lh> <n9i565F6v2gU2@mid.individual.net> <8idu6g1pxnf.dlg@v.nguard.lh> <n9imgiF97blU2@mid.individual.net> <1htmjbmsfyz04$.dlg@v.nguard.lh> |
On 2026-06-19 08:05, VanguardLH wrote:
> "Carlos E. R." <robin_listas@es.invalid> wrote:
>
>> My main question is if companies switching to sending RCS instead of SMS
>> would avoid impersonating the sender, because RCS uses certificates. On
>> the other hand, one certificate exchange per client in the database...
>
> From what I've found about RCS, yes, it uses encryption to secure the
> messages. That's just encryption, not identification. I've heard about
> RCS spam for quite a while. I doubt spammers want to be exposed.
>
I have not seen any spam on RCS.
There are certificates exchanged on each pair of people, it is the basis
of the system discussed in the thread "Android will detect calls with
spoofed numbers by sending a real-time RCS message to the legitimate owner"
It is not about encryption but identification, signatures.
...
> At this point, I don't think you got phished. I think your dental
> provider had a hiccup in their accounting system, or someone there
> entered the wrong account in the notice you got. The text you got only
> mentions a claim number, not your name, account number, or any other
> identifying information of your business with them. Adding identifying
> info in a text would make it larger, and they may be restricting their
> texts to the old 160-character limit of SMS.
The insurance claim was true, just assigned to the wrong ID. It was
legitimate, but they have a bad software system. This was explained on
another message here.
> Was the bogus message sent using RCS, or just SMS?
Just SMS.
> RCS messages should
> show Encrypted with a padlock icon at the top. Some will show RCS
> messages in a differently colored bubble. Some show a shield icon with
> a checkmark. Apple's iMessage shows a "<padlock> Encrypted" at the top
> of an RCS message. How to differentiate SMS from RCS depends on which
> messaging app you use.
>
>
> <Aside - Read Receipts>
I leave read receipts active on WhatsApp. I don't care if they see I
have read and not replied. I prefer to know that a message has been read.
--
Cheers,
Carlos E.R.
ES🇪🇸, EU🇪🇺;
Back to comp.mobile.android | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 10:01 +0200
Re: SMS spoofing VanguardLH <V@nguard.LH> - 2026-06-18 03:36 -0500
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 14:04 +0200
Re: SMS spoofing Andy Burns <usenet@andyburns.uk> - 2026-06-18 13:07 +0100
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 14:18 +0200
Re: SMS spoofing VanguardLH <V@nguard.LH> - 2026-06-18 08:40 -0500
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 19:00 +0200
Re: SMS spoofing AJL <noemail@none.com> - 2026-06-18 18:08 +0000
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 20:49 +0200
Re: SMS spoofing VanguardLH <V@nguard.LH> - 2026-06-19 01:05 -0500
Re: SMS spoofing Andy Burns <usenet@andyburns.uk> - 2026-06-19 07:46 +0100
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-19 12:12 +0200
Re: SMS spoofing VanguardLH <V@nguard.LH> - 2026-06-20 03:14 -0500
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-20 10:25 +0200
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-19 12:11 +0200
Re: SMS spoofing Andy Burns <usenet@andyburns.uk> - 2026-06-18 10:13 +0100
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 14:05 +0200
Re: SMS spoofing Theo <theom+news@chiark.greenend.org.uk> - 2026-06-18 11:38 +0100
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 14:10 +0200
Re: SMS spoofing Philippe <p.naudin+nntp@free.fr> - 2026-06-18 14:48 +0200
Re: SMS spoofing VanguardLH <V@nguard.LH> - 2026-06-18 08:57 -0500
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-18 19:14 +0200
Re: SMS spoofing AJL <noemail@none.com> - 2026-06-18 15:56 +0000
Re: SMS spoofing Jörg Lorenz <hugybear@gmx.net> - 2026-06-19 09:13 +0200
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-19 12:13 +0200
Re: SMS spoofing Jörg Lorenz <hugybear@gmx.net> - 2026-06-19 14:16 +0200
Re: SMS spoofing Theo <theom+news@chiark.greenend.org.uk> - 2026-06-19 17:22 +0100
Re: SMS spoofing Jörg Lorenz <hugybear@gmx.net> - 2026-06-19 21:23 +0200
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-20 01:17 +0200
Re: SMS spoofing "Carlos E. R." <robin_listas@es.invalid> - 2026-06-20 01:14 +0200
csiph-web