[softwarelist] Re: SparkFS problem
- From: Alan Dawes <alan.dawes@xxxxxxxxxxxxx>
- To: davidpilling@xxxxxxxxxxxxx
- Date: Sun, 07 Aug 2016 12:03:44 +0100
On 07 Aug, Dave Symes <dave@xxxxxxxxxxxxx> wrote:
In article <4061d5f1-4c6e-54f9-03ca-16d05d8957c3@xxxxxxxxxxxxxxxxxxx>,
David Pilling <david@xxxxxxxxxxxxxxxxxxx> wrote:
Hi Dave,
On 06/08/16 22:32, Dave Symes wrote:
I have a Sparkfile that's password protected and I've just discovered
after sticking a load of files in it that my file names have all been
truncated at 13 characters. (Expletive).
Because the Spark file format predates long file names, both in RISC
OS and in MS DOS which is what the format is based on.
Zip files have no such limits (but do not support encryption in
SparkFS).
Info-zip may help.
Thanks.
Not quite sure how Info-Zip might help?
I see no encryption option in the version I have (3.02).
I've not used !Infozip on RiscOS but the routines for password encrypting
and decrypting are in the latest !Infozip 3.07 on Harriet's site:
http://www.starfighter.acornarcade.com/mysite/utilities.htm
but you may need to go to the command line to use them.
The !Infozip.Routines.unzip/txt in her version says:
"-P password use password to decrypt encrypted zipfile entries (if
any). THIS IS INSECURE! Many multi-user operating
systems provide ways for any user to see the current command
line of any other user; even on stand-alone systems there
is always the threat of over-the-shoulder peeking. Storing
the plaintext password as part of a command line in
an automated script is even worse. Whenever possible, use
the non-echoing, interactive prompt to enter passwords.
(And where security is truly important, use strong
encryption such as Pretty Good Privacy instead of the
relatively weak encryption provided by standard zipfile
utili- ties.)"
and in !Infozip.Routines.zip/txt says:
"-P password
--password password
Use password to encrypt zipfile entries (if any). THIS IS
INSECURE! Many multi-user operating systems provide ways for
any user to see the current command line of any other user;
even on stand-alone systems there is always the threat of
over-the-shoulder peeking. Storing the plaintext password as
part of a command line in an automated script is even worse.
Whenever possible, use the non-echoing, interactive prompt to
enter passwords. (And where security is truly important, use
strong encryption such as Pretty Good Privacy instead of the
relatively weak standard encryption provided by zipfile
utilities.)"
Alan
--
alan.dawes@xxxxxxxxxxxxx
alan.dawes@xxxxxxxxxx
Using an ARMX6
To unsubscribe or subscribe goto:
//www.freelists.org/list/davidpilling
Other related posts:
