Hi!
You're discussing for quite a long time about ARJ Z ...
I fear none of you has ever read the DOCumentation...
HM>> If I run "ARJ Z ARJ250A.EXE", which has a security envelope, I get
HM>> the error message:
HM>>             Can't update an ARJ-SECURED archive!
That's okay since Secured ARJives may not be altered
HM>> If I run the same command on an archive without security envelope,
HM>> for example:
HM>>                      ARJ Z ZTest.arj
HM>> I get: ...
  > >Bad or missing SECURITY key
That's okay since you haven't (at least I'm sure you haven't) paid for a  
security key (RTFM):
     ARJ_SECURITY ENVELOPE:
        The ARJ-SECURITY ENVELOPE feature provides a facility similar to
        other archivers.  This feature disallows any type of modification,
        even commenting, to an ARJ-SECURED archive by ARJ.  Moreover, there
        are additional internal checks to determine if the ARJ-SECURED
        archive has been modified in any way.
                                              *This EXTRA cost feature is*
        *intended for use by software developers who distribute their*
        *software in archived format and is only available for a special*
        *fee.*
              However, there can be no guarantee that this mechanism cannot
        be defeated.
        When accessing an ARJ-SECURED archive, ARJ will display a message
        indicating that ARJ is verifying the security envelope.  If the
        envelope is damaged, a message will be displayed indicating so.
        If the envelope is intact, then the ARJ-SECURITY signature of the
        user locking the archive will be displayed.
        If the security envelope has been tampered with or the archive has
        suffered data corruption, ARJ will display a message stating that
        the security envelope has been damaged.  In addition, ARJ will not
        abort processing the archive.  The ARJ "-he" option and the ARJSFX
        "-s" option will skip the envelope verification.  The most likely
        causes of an invalid envelope are that the file was corrupted in
        transmission or that the archive was tampered with.
--- uuuund wech....
---------------