On 9/25/07, Daniel Senie <dts@xxxxxxxxx> wrote:
You have the other problems listed above in this case (manual exchange difficult etc.
and the other problems listed in my original mail).
Why the CAPTCHA solution is not enough for you? In my personal view, the person who
wants to disturb you is the one who is suffering (CAPTCHAs can be made very hard
if you wish).
Maybe it wasn't clear. Here are the steps:
The querier user makes the request.
The target phone returns a CAPTCHA.
The querier user solves the CAPTHA.
The target user sees the query displayed on the screen and approves the request (or not).
The phone number is returned (or not).
Thanks,
pars
At 03:02 PM 9/25/2007, Pars Mutaf wrote:And hopefully this can all be FULLY disabled, or be disabled by default. Otherwise, everyone will be inundated with these messages popping up, asking you to hit the "yes" button. Count me as someone who'd never want this protocol implemented in my phone.
On 9/25/07, Pars Mutaf <pars.mutaf@xxxxxxxxx> wrote:
- Hello,
- On 25 Sep 2007 16:33:32 -0000, John Levine < johnl@xxxxxxxx> wrote:
- >1. The querier user types the target user's "human name" (as if he were
- > consulting a phonebook), or a pseudoynm.
- >2. The pairing request is forwarded to the target phone.
- >3. The query, along with the querier user's name, are displayed on the
- > target phone's screen.
- I have a list of 250,000 people here (scraped off web sites) to whom
- I'd just love to make recorded phone calls. Can I use your protocol
- to ask them all if it's OK? If not, why not, and how are you going to
- stop me?
- Using a Turing test (CAPTCHA) for example.
- http://en.wikipedia.org/wiki/Captcha
- When you make a request, the target phone returns a captcha. If you
- don't provide the right solution, the target user won't even see your
- request, it will be dropped. Captcha's difficulty can be adaptively
- tuned by the target phone..
- So another step should be added to the above description.
A quick addition to my previous mail:
Captcha is proposed for protecting the target user against
disturbing bogus requests.
There is also the 4th step (below) in the original mail which suggests
that user approval is needed before the phone number
(or any info you like) is returned to the querier:
4. The target user approves the request in real-time by pushing on the YES
button of the phone.
You have the other problems listed above in this case (manual exchange difficult etc.
and the other problems listed in my original mail).
Why the CAPTCHA solution is not enough for you? In my personal view, the person who
wants to disturb you is the one who is suffering (CAPTCHAs can be made very hard
if you wish).
Maybe it wasn't clear. Here are the steps:
The querier user makes the request.
The target phone returns a CAPTCHA.
The querier user solves the CAPTHA.
The target user sees the query displayed on the screen and approves the request (or not).
The phone number is returned (or not).
Thanks,
pars
Regards,
pars
- I hope this answers your question!
- Regards,
- pars
- Regards,
- John Levine, johnl@xxxxxxxx, Primary Perpetrator of "The Internet for Dummies",
- Information Superhighwayman wanna-be, http://www.johnlevine.com , ex-Mayor
- "More Wiener schnitzel, please", said Tom, revealingly.
_______________________________________________
Ietf@xxxxxxxx
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf