Jump to content

Restrict created file access


Angelo.

Recommended Posts

Hello,

I'll get straight to it.
I'm trying to restrict access to an XML file which I'm planning to create. This file will contain more or less sensitive information which I don't want clients to access.
Usually, when a file is created by a resource, clients can find it in the downloaded resources folder. In my case I don't want that to be possible.
I thought about deleting the file after using it, but the file will be edited via a GUI which I coded by people with proper access.

Is it possible to have the file created and hidden from clients? not sure if it works similar to server scripts which are not downloaded by clients. Or maybe create the file but only for specific clients?

Link to comment

If they have the key for it, sure.
Another option would be to have the file on the server side and only cache it on the client side.

Although I don't think clients should have any sensitive data at all saved to their disk, their password (encrypted ofc) would be the only sensitive data I'd let a client save...so you might want to think of another way to do this.

Link to comment
5 hours ago, 3aGl3 said:

If they have the key for it, sure.
Another option would be to have the file on the server side and only cache it on the client side.

Although I don't think clients should have any sensitive data at all saved to their disk, their password (encrypted ofc) would be the only sensitive data I'd let a client save...so you might want to think of another way to do this.

is it possible to have the file created on the server only? If yes, that's what exactly I'm looking for.

Link to comment
1 hour ago, Angelo. said:

Cool, I wasn't sure it was possible. So I'll just create the file server side and not include it in the meta so clients won't download it.

u r create new file with key (encode)

after that u decode with key on client side with client files in cache

so:
1) meta xml
2) client.lua
3) server.lua

all files, but 2 and 3 encode with key, this files users download then decode and users client apply this in server
so, users take only encode files and algorythm for decode - then take cookies ;)

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...