<html><head></head><body><div class="ydpf579ac79yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;"><div></div>
<div dir="ltr" data-setdir="false">I figured if Caller ID said "Unavailable", it probably wasn't anyone I knew or wanted to talk to, but they kept calling all afternoon. </div><div><br></div>
</div><div id="ydp3140e27cyahoo_quoted_1634200159" class="ydp3140e27cyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, August 19, 2022 at 04:56:17 PM PDT, Rick Moen <rick@linuxmafia.com> wrote:
</div>
<div><br></div>
<div><br></div>
<div>Quoting Paul Zander (<a href="mailto:paulz@ieee.org" rel="nofollow" target="_blank">paulz@ieee.org</a>):<br><br>> A bogus email is less annoying than spam phone calls. A week or two<br>> ago, I received 8 phone calls all from "unavailable". All left voice<br>> mail saying it was Amazon calling about an order for an iPhone. Press<br>> #1 to confirm; Press #2 if I didn't place the order.<br><br>tl;dr: Incoming voice calls (and CallerID[1]) are unauthenticated.<br>Everything else flows naturally from that.<br><br>[1] The IETF SHAKEN/STIRRED auth. protocols should remediate this<br>partially, as it gets rolled out, but CallerID still should not be<br>relied upon.<br><br><br>_______________________________________________<br>conspire mailing list<br><a href="mailto:conspire@linuxmafia.com" rel="nofollow" target="_blank">conspire@linuxmafia.com</a><br><a href="http://linuxmafia.com/mailman/listinfo/conspire" rel="nofollow" target="_blank">http://linuxmafia.com/mailman/listinfo/conspire</a><br></div>
</div>
</div></body></html>