[VOIPSEC] A Simple Asterisk Based Toll Fraud Prevention Script
Zmolek, Andrew (Andy)
zmolek at avaya.com
Sun Feb 8 17:48:58 CST 2009
Perhaps it's time for us in the VOIPSEC community to create the SPIT &
Toll Fraud equivalent of what regular slashdot readers know as the
"Universal Crackpot Spam Solution Rebuttal Form" at
http://craphound.com/spamsolutions.txt (and essentially unmodified
below):
=======================================================
Your post advocates a
(X) technical ( ) legislative ( ) market-based ( ) vigilante
approach to fighting spam. Your idea will not work. Here is why it won't
work. (One or more of the following may apply to your particular idea,
and it may have other flaws which used to vary from state to state
before a bad federal law was passed.)
( ) Spammers can easily use it to harvest email addresses
( ) Mailing lists and other legitimate email uses would be affected
( ) No one will be able to find the guy or collect the money
( ) It is defenseless against brute force attacks
( ) It will stop spam for two weeks and then we'll be stuck with it
( ) Users of email will not put up with it
( ) Microsoft will not put up with it
( ) The police will not put up with it
( ) Requires too much cooperation from spammers
( ) Requires immediate total cooperation from everybody at once
( ) Many email users cannot afford to lose business or alienate
potential employers
( ) Spammers don't care about invalid addresses in their lists
(X) Anyone could anonymously destroy anyone else's career or business
Specifically, your plan fails to account for
( ) Laws expressly prohibiting it
( ) Lack of centrally controlling authority for email
( ) Open relays in foreign countries
( ) Ease of searching tiny alphanumeric address space of all email
addresses
(X) Asshats
( ) Jurisdictional problems
( ) Unpopularity of weird new taxes
( ) Public reluctance to accept weird new forms of money
( ) Huge existing software investment in SMTP
(X) Susceptibility of protocols other than SMTP to attack
( ) Willingness of users to install OS patches received by email
( ) Armies of worm riddled broadband-connected Windows boxes
( ) Eternal arms race involved in all filtering approaches
( ) Extreme profitability of spam
( ) Joe jobs and/or identity theft
( ) Technically illiterate politicians
( ) Extreme stupidity on the part of people who do business with
spammers
( ) Dishonesty on the part of spammers themselves
( ) Bandwidth costs that are unaffected by client filtering
( ) Outlook
and the following philosophical objections may also apply:
(X) Ideas similar to yours are easy to come up with, yet none have ever
been shown practical
( ) Any scheme based on opt-out is unacceptable
( ) SMTP headers should not be the subject of legislation
(X) Blacklists suck
( ) Whitelists suck
( ) We should be able to talk about Viagra without being censored
( ) Countermeasures should not involve wire fraud or credit card fraud
( ) Countermeasures should not involve sabotage of public networks
( ) Countermeasures must work if phased in gradually
( ) Sending email should be free
( ) Why should we have to trust you and your servers?
( ) Incompatiblity with open source or open source licenses
(X) Feel-good measures do nothing to solve the problem
( ) Temporary/one-time email addresses are cumbersome
( ) I don't want the government reading my email
(X) Killing them that way is not slow and painful enough
Furthermore, this is what I think about you:
(X) Sorry dude, but I don't think it would work.
( ) This is a stupid idea, and you're a stupid person for suggesting it.
( ) Nice try, assh0le! I'm going to find out where you live and burn
your
house down!
/\\//\Y/\ Andy Zmolek | zmolek at avaya.com | 303-538-6040
GCS Security Technology Development | Avaya, Inc.
-----Original Message-----
From: voipsec-bounces at voipsa.org [mailto:voipsec-bounces at voipsa.org] On
Behalf Of Hendrik Scholz
Sent: Saturday, February 07, 2009 9:59 AM
To: J. Oquendo
Cc: voipsec at voipsa.org
Subject: Re: [VOIPSEC] A Simple Asterisk Based Toll Fraud Prevention
Script
Hi!
What would happen if I just send REGISTERs with broken/wrong
Authorization: headers?
Looking at check_auth() in chan_sip.c there is no difference if the
nonce was offered by the Asterisk machine itself or it was just a random
one I came up with.
That way an attacker could spoof a source IP, send a single REGISTER
with random Authorization:.
Your script would trigger and blog a possibly legitimate source (i.e.
your outbound SIP trunk ;)).
Just my $.02,
Hendrik
--
Hendrik Scholz <hs at 123.org>
_______________________________________________
Voipsec mailing list
Voipsec at voipsa.org
http://voipsa.org/mailman/listinfo/voipsec_voipsa.org
More information about the Voipsec
mailing list