Wasn't tru64 unbreakable too? *scratches head*
-simon
-Original Message-
From: KF (lists) <[EMAIL PROTECTED]>
To: full-disclosure@lists.grok.org.uk
Sent: Tue, 17 Jan 2006 17:09:54 -0500
Subject: Re: [Full-disclosure] Oracle Reports - Read parts of files via
customize(fixe
un·break·a·ble (un-bra'ka-bal) pronunciation
adj.
1. To brush holes under rug as long as possible.
2. Able to hide beind a garbage Ad campaign.
http://www.oracle.com/oramag/oracle/02-mar/o22insight.html
Whats Behind it you ask? How about a nice big fat steamy load of poopy.
-KF
Thierry Zoller
Dear Alexander Kornbrust and Amichai Shulman ,
It's astonishing how customers are left vulnerable for _years_ trying
to conceal hundreds of bugs under a single patch. Knowing what type
of sensitive data I have come across on certain Oracle servers
I wonder whether this strategy pays out for Oracle
Hello FD-Reader
It took only 875 days to fix this problem.
Summary and additional information concerning the Oracle January 2006
CPU is available here:
http://www.red-database-security.com/advisory/oracle_cpu_jan_2006.html
##
http://www.red-database-security.com/advisory/oracle_reports_
