Hi,
(Sorry if this not the right place to ask these questions but I don't see
an e-mail address or a better place to post.)
I'm interested in using your program but have a couple of questions/concerns.
Basically the system would be used to store and share files from different
security assessment projects and the associated documentation.
What I need to do is to limit access to a given directory and its files to
just the selected list of people authorized to work on a given project.
I.e., Joe could open the following directory and copy or download a file from:
----->PSE
File A
File B
(etc.)
but would not have access to:
----->Swedish
File A
File B
(etc.)
while Bob could access:
----->Swedish
File A
File B
(etc.)
but would not have access to:
----->PSE
File A
File B
(etc.)
I also need to make it mandatory that a file is never overwritten but a new
file created when a file of the same name is saved. So a file that might
exist would be:
BigDamnReport_20100419.zip
If someone were to download this file, edit it and then upload it it would
automatically get a new name something like:
BigDamnReport_20100419(A).zip
The reason for this is to preserve prior versions for comparison. However I
can not use a file locking mechanism (CVS/SVN and such) as is used in
software development as multiple people might be working on or using a
given file at the same time, not sequentially, and their additions or
corrections need to be captured by individual author for later review purposes.
Can this be accomplished with your program?
Warmest Regards,
Allen Schaaf - CISSP, CEH, CHFI, CEI, CSCA
Information Security Analyst - Business Process Analyst
Training & Instructional Designer - Sr. Writer & Documentation
Developer - Certified Network Security Analyst & Intrusion
Forensics Investigator - Certified EC-Council Instructor
http://www.linkedin.com/in/allenschaaf
Security is lot like democracy - everyone's for it but
few understand that you have to work at it constantly.
Original issue reported on code.google.com by li...@cyberonic.com on 21 Apr 2010 at 4:43
Original issue reported on code.google.com by
li...@cyberonic.comon 21 Apr 2010 at 4:43