Re: Mochasoft security hole

Ah HA !

That was in theory what I though might have been happening - not sure why I had 
that
thought :-)

Just saw Chuck Morehead's post to set it to 0. Here is yet another strange 
one... We
have ours set to 1. I'm guessing it creates one new virtual device and then no 
more
? Here is why. Running NT and attaching to the AS/400 with TCP/IP via Synapse's 
5250
IP product, we set the PC name to what we want the device to be and then the 
5250
product adds and Sn (where n is a number starting with 1) to the end of that 
(i.e.
PC name is GR30 so first 5250 session is GR30S1, second is GR30S2, etc.). I was
setting up a new device yesterday and it would not create, until I increased the
QAUTOVRT value...

Another nasty about this way - there is no message sent to QSYSOPR when a 
device is
created this way ! Why not I wonder; were they afraid that would cause to many
messages with QPADEVxxx's or something ? I think that would be an acceptable 
risk
and at least you could monitor for it... (?)

Chuck

glea@dextermag.com wrote:

> I tried this and the creation date and time were exactly at the time we were
> doing the testing.  Apparently the existing device description was deleted 
>and a
> new one created in a varied on state.  Scary!  Will setting QAUTOVRT to zero
> prevent this?
>
> Gary Lea