× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. July 2007

RE: Check constraints was: Imbedded SQL vs Sequence object

From: rob@xxxxxxxxx

True on both counts Joe. If your security is so blown that you are
relying upon "security by obscurity" you have serious issues to deal with.

How is denying unrestricted public access to data security by obscurity?


While there is something to be said for "defense in depth" security by
obscurity is so weak it's like hoping that crepe paper streamers will stop
infiltrators who have gotten past artillery bombardments, mine fields,
tank traps, triple concertina wire, ditches filled with water covering
pungee sticks, overlapping fields of fire from machine guns and various
weapons of air dominance.

A fine mental picture, but it has absolutely nothing to do with putting
*PUBLIC *EXCLUDE access on your database.


I love how you carry on these arguments. First, you use a term incorrectly
and then you complain about the term that you incorrectly used. If you
continue to feel the need to argue with yourself, please find a nice quiet
place with a mirror.


Joe



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.