In 050701d02c6d$4c43bef0$e4cb3cd0$@mcn.org, on 01/09/2015
at 04:35 PM, Charles Mills charl...@mcn.org said:
A stitch in time saves nine.
Whoosh!
Let me rephrase that in simple terms. Have there been any successful
cracking attempts in the wild against real, present-day mainframes
that
On Sat, 10 Jan 2015 14:40:19 +0100, Bernd Oppolzer bernd.oppol...@t-online.de
wrote:
for batch programs, a table space scan on large tables may well be
the best access strategy, if the related SQL is the overall cursor
controlling
the batch program, and if large portions of the table is used. So
Do I know about a violation of the statement of integrity that IBM has not
addressed? No, of course not.
I am not certain that MVS exposures versus lax security is a black and
white dichotomy. It's easy to look after the fact at any breach and say
aha! You should not have done X. I don't think
Ye all,
goes to show that all exposures are dangerous.
Never wear a mini skirt in winter. Especially this winter (IBM is dead) of
discontent.
Batten yer hatches and be happy that in years of yore things were good.
All the best - and batten yer bleedin hatches again.
Andre
= Do I know
I think the Logica breach is a perfect example of the problem in many ways.
I don't think anyone knows for certain how Gotfridd Warg got into Logica
initially. (He has been convicted so I do not have to say allegedly.)
However, it is clear he was not an insider or anything like that. One
Walter Bass writes:
And now they will take Data Studio away from us when we
don't use it frequently enough because licenses are expensive
and we can see that you are not using the product.
If Visual Explain had a licensed/paid option our company
would buy it and give us access to it. Big
charl...@mcn.org (Charles Mills) writes:
I am not certain that MVS exposures versus lax security is a black and
white dichotomy. It's easy to look after the fact at any breach and say
aha! You should not have done X. I don't think the role of we security
practitioners is solely pointing out
