[Asterisk-Users] Blocking the 'Do Not Call" List

[Chris Shaw]

That is a matter of opinion and not in any way factual.... SQL, just as
everything else, is as secure as YOU make it... As you said, it's a language
for querying relational databases, it has no knowledge of security. That's
what firewalls, encryption and strong passwords are for...

However, for the purpose of blocking numbers based on a do-not-call list, it
will work perfectly fine. It's lightweight, fast and relatively efficient...

    -Chris

----- Original Message -----
From: "Peter Corlett" <abuse at cabal.org.uk>
Newsgroups: newsgate.asterisk-users
To: <asterisk-users at lists.digium.com>
Sent: Wednesday, August 11, 2004 9:19 AM
Subject: Re: [Asterisk-Users] Blocking the 'Do Not Call" List


> Gabriel Millerd <gmillerd at gmail.com> wrote:
> [...]
> >> If "less than a second" implies "best part of a second", then
> >> that's a bit slow, although probably still good enough for this
> >> application. (But I personally avoid MySQL for security reasons.)
>
> > how is SQL insecure?
>
> SQL itself is just a standard for querying relational databases, and
> does not in itself specify or require security, nor does it have
> inherent security problems.
>
> MySQL is a toy database that mostly ignores all but the most
> superficial of the SQL standard and has a large catalogue of
> bugs and misfeatures that can cause silent data corruption.
>
> --
> First they blacklisted the porno spammers and I emailed nobody for I was
not a
> porno spammer. Then they blacklisted the open relays and I emailed nobody
for I
> was not an open relay. Then they blacklisted the ISP dialup subnets and I
> emailed nobody for I was not on an ISP dialup subnet. Then they
blacklisted
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users