accounts in the VFS instead of INI

Mars · **on:** October 23, 2007, 09:36:03 PM

rejetto

user accounts are saving in ini file, is it posssible to store them into vfs file with the directory and permissions for users
i think it's more logical, when your load a file system vfsto have account in it.

when i start differents fvs accounts and folders restrictions even necessarily are not

rejetto · **Reply #1 on:** October 23, 2007, 09:41:04 PM

i put them in the ini so to have accounts shared between different VFSs
but it's disputable
any other opinion?

bacter · **Reply #2 on:** October 23, 2007, 10:22:12 PM

I think the user accounts don't have to be in the vfs for different reasons:

- If I change structure of the vfs in a new directory or on another machine, leaving the old one working until finished, then I create
a new vfs. And there would be a problem move the account list.

- A solution could be let the account list by default in the ini file, but with a new option: external account-file=useracc.lst

The latter would be usefull if we think in larger account lists in a future implementation of user-groups that would simplify
administration!

Mars · **Reply #3 on:** October 23, 2007, 10:49:25 PM

user accounts and folder restrictions are linked , we can load a vfs file (with account into ) and clear all folders in hfs to create another vfs file with same accounts.

If accidentally your ini file is destroyed, then there is not means anymore to connect the vfs with the lost accounts it is necessary to redo everything and it is not of the tart past certain number of users and folders

when i change my vfs loading, they are generaly not the same user accounts i have

the actualy possibility is too restrictive

an option like "include accounts into vfs file instead ini file" into menu "virtual file system", It would be I think of a good compromise for our opposite points of view

ELEVENNNN · **Reply #4 on:** October 23, 2007, 10:57:04 PM

It seems like people are trying to change things randomly lately, assuming people run different instances that run as servers per se, being able to change the vfs and change the associated user accounts has some possibilites.. perhaps just a menu option to toggle between the way the accounts are refrenced. Like how hfs has Save -> To config file or To registry. You could also have Associate accounts by -> VFS or Config File (Ini)

What do others think, and why dont i ever use smiies..

Mars · **Reply #5 on:** October 23, 2007, 10:59:23 PM

you repeat what i have already say above

ELEVENNNN it's not serious, it is the same problem when in a car two drivers want to take the steering wheel at the same time

ELEVENNNN · **Reply #6 on:** October 24, 2007, 05:47:49 AM

Look at the post times mars, I was working and started the post while you wrote yours and click submit I was making a run to fix something, I came back, added a few more sentences, and hit submit. I'm sorry about that though :|

Foggy · **Reply #7 on:** October 24, 2007, 06:41:40 AM

Quote from: mars on October 23, 2007, 10:59:23 PM

you repeat what i have already say above

Great minds think alike

I think choice to save accounts in either the ini or the vfs is a good idea but personally I think that the accounts should be stored in the vfs file because the vfs contains the folders/files which the account refers to.

After typeing that I was thinking that it wouldnt matter where the accounts are stored as long as the user permissions are stored in the vfs.

Foggy · **Reply #8 on:** October 24, 2007, 06:47:14 AM

I was just reading another post and I had the idea that if hfs loads a vfs file and finds permissions for an acount that doesnt exist, hfs should alert the user and/or offer to create the account.

rejetto · **Reply #9 on:** October 24, 2007, 02:12:29 PM

it will not be an option.
it's something that should be in a way by design.

dardarlt · **Reply #10 on:** October 24, 2007, 09:39:46 PM

Quote from: mars on October 23, 2007, 09:36:03 PM

user accounts are saving in ini file

Could anyone explain how to save user accounts in .ini file and to make and to make, that HFS would read this file?

Mars · **Reply #11 on:** October 24, 2007, 10:52:05 PM

user accounts are saving in file hfs.ini (if your version of hfs is not old) at line accounts=login:.... this file is read at run hfs

in hfs MENU -save options- you select "to file" and check "auto save options on exit"

MarkV · **Reply #12 on:** October 26, 2007, 09:25:34 AM

Q: Accounts in VFS or in *.INI?
A: In both.

There should be two types of accounts.

Type 1: These are 'normal' accounts. When a normal account is created, it saves to the current VFS and is valid for this VFS only.
Type 2: These are 'shared' accounts. On creation, they are saved to the current VFS and to the *.INI. If the user then creates a new VFS, all shared accounts are copied over from the *.INI to the new VFS.

On account creation/modification, there simply would be a checkbox where you can mark/unmark an account as 'shared'
In case of conflicting accounts, the VFS should override the *.INI.

This is my suggestion.

bacter · **Reply #13 on:** October 26, 2007, 11:56:57 AM

We se several proposals where to store the useraccounts vfs, ini and both.

I insist that the solution with most future would be a third,external file for this purpose, something like useracc.lst

I have some reasons to believe that:
- if someone uses different vfs, he may be free to copy the accountfile with the vfs
- as the account-list may grow considerably in some cases, ini and vfs may grow a lot.
- thinking about different requests seen about account related questions, a separate file
could permit people to implement some 'rare' features outside hfs, as complement. Like this:

The only restriction for that file would be initially, that each register (starting with login:) maintains the first fields exactly the same way as does the actual format in the ini file, what should mean less work for rejetto to change the system. But after the actual values, programmers may add extra fields that hfs could ignore for now. Perhaps it would be nice if we could terminate each registry entry with a <CR> or line break.
With this feature we could help massimo to do more essential modifications on hfs, leaving some special questions for special features to other coders without interfering in Massimo's code. To explain the needed tool I will open a separate feed.

Here I will only mention what benefits we could have (making small tools for it):

somebody might add fields like: creation_date, expire_date, last_login_date, total_download_files,total_download_size, total_upload_files, total_upload_size etc. Then browsing periodically the historyfiles he can update those values
somebody could write a cleanup program that willl eliminate users with a set expire_date or who's last_login last from more than two months etc.
somebody could write a account creating program with the help of the feature 'external commands' (new thread) etc... etc..

If we want to change the location of the accounts from ini to vfs or both, I think it's better to move it outside, only adding a commandline option to hfs: -ru (reload useraccounts) that could be executed if we add or delete or ban users from outside.