RE: Why NOT the web?

[rob@xxxxxxxxx]

http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/6f5f6a97c126608e86256e21004d0e9a?OpenDocument
http://www-912.ibm.com/a_dir/as4ptf.nsf/a18db68aae4a7d81862566ba005d145c/afe8220b54a9933d86256f7800735e4e?OpenDocument
...
You tell me how they work.

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





"Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
12/30/2004 02:42 PM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: Why NOT the web?






> From: rob@xxxxxxxxx
> 
> And, again, you don't see that about IBM bugs because they practice
> security by obscurity.  If you search the ptf cover letters for
Integrity
> problem it will not tell you that if you don't put this on someone can
> take over your system, they just simply say "Integrity problem".  And
if
> you search all ptf cover letters you get 250 hits.  And that's just
the
> integrity problems - let alone all the OS failures, websphere
failures,
> etc.

I have no idea what you're saying here, Rob.  Are you saying there are
250 PTFs that you KNOW allow someone to completely take over an iSeries
machine?  How is this done?  Through TCP/IP?  Through adopting user
profiles?  Through a breakdown in object security?

Security by obscurity is certainly a problem, as Leif was always wont to
point out, but condemnation by obscurity is just as bad.  Please tell me
a dozen or so of the PTFs that allow security breaches and how they
work.

Joe

-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.