Subject: | |
From: | |
Reply To: | |
Date: | Thu, 24 Jan 2002 10:49:08 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
> -----Original Message-----
> From: John Pollard
>
> And, yes, MPEX can do this - my one small nit to pick is that MPEX
> creates a PRIViledged file (JOBSAVE's file is not PRIV) which
> adds some work to our method of handling saved jobs.
That "nit" is intentional -- it is a small homage to security as the file of
saved jobs contains plaintext passwords and lockwords. Making it a PRIV
file reduces the opportunities for a cracker to gain access. OTOH: since
you have MPEX, you *could* use MPEX to alter the filecode to a positive
value, thus removing the PRIV file restriction [but you need to remember to
change it back when re-submitting the jobs]
I suppose a better solution would be to encrypt the file, but two-way
encryption is getting more and more trivial to break, and in this case, it
is fairly easy anyway -- certain characteristics of jobs makes it easy to
spot patterns in an encrypted file [most lines begin with "!"; jobs start
with !JOB XXXX... and end with !EOJ; etc.]
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|