Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I am not an expert but I have a few suggestions,<br> ('user' is considered Male here) </p> <p>In Windows, when an user is logged in, he will have all the rights to manipulate a file or folder which belongs to him.<br> But, if he tries to manipulate files or folders which belong to other users, he is not allowed to do so. So, he can't manipulate other user's files.<br> If the user is administrator, he will have all the rights to manipulate the file.<br> In your case, I believe the user is not administrator. </p> <p>So, <strong>I suggest</strong> to you to:<br> Create a user for this application, say Bob(Bob is not the user who is going to use this application).<br> Then you create a folder to store your files and give all permission only to Bob(and the admin).<br> For all others, there no permission to do anything to the folder.<br> <strong>Your application must be installed by administrator</strong>. </p> <p>When you start, Your application asks Bob's password from current user.<br> If the password is correct,<br> Using your application allow full access folder permission to the current user. Then application can work as you wish.<br> If the user quits the application,<br> Remove all permission for current user so that after quitting this application others can't access that content.<br> But Administrator can still access this content.</p> <p>This is similar like Linux user management.<br> When you are getting a shell you can change user using <code>su username</code> when finishes the work and he quits the shell then others can't use those files. But root user can do anything in Linux. </p> <p><strong>But there is one problem</strong>.<br> Administrator can get full content and access since he can modify the permissions.<br> To disallow this, save the files by zipping using any technique and by using a password. That password is only known by the user who uses it. Before saving a file to the folder, zip it using a password. Before using the file, unzip it using the password. </p> <p>If the zipping password is same as user password, then there is a problem.<br> The administrator can reset user password to something and open his account.<br> To prevent this you can use the following technique:<br> Use zip password as reverse of user password, so that if his password is 1234 the zipping password is 4321, or use hash value of user password as zipping password.<br> If the zip password is hash value like MD5 hash or SHA-1 then brute force on zip file won't work due to the password length.<br> I don't know if this is a working solution or not or if this can be implemented or not.<br> But you can take some ideas out of this, if you think there is some good ideas in this.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload