index
netauth installation guide
netauth allows minux computers to connect to a central server for their user accounts
it contains a client and server side package each with it's own commands and functions
it also requires a working ccDns-server to operate properly
make sure that your server is on a chunk that is also loaded when the clients log in

the client will connect to the server whenever a login or other account action is attempted,
the client finds the server by it's ccDns name, allowing the server to be changed if blown up by a creeper.
the server will then verify if said user is allowed to or not based on it's database of users.


1 - ccDns server
we start with our ccDns server, this needs to be an advanced computer, if your network already has one you can skip this stage and use that one.
the dns server is used to translate computer id's into names, this allows the id to be changed at any time redirecting clients to the new system.

- install minux using "wget run https://enoua5.github.io/cc-minux-repo/netinstall", select the minimal installation option.
- disable crashhandler by using "config set crashhandler false", this because the server will never really shut down properly and would trigger said crashhandler.
- enable local user accounts using "config set login true", chose your root password.
- create a new user to register domains with using "useradd username password".
- install the server package using "mapt install ccdns-server", restart the system.
- register the auth-server system on the dns using "ccdns register authserver ID owner netauth-server", change ID to the netauth-server's ID and if you want the owner and description to


2 - netauth-server
next up is our netauth server, again we need an advanced computer, this can be the same system as the dns server but this does slow it down.
we will configure the system, register it on the dns, install the server and then create an admin user.

- install minux using "wget run https://enoua5.github.io/cc-minux-repo/netinstall", select the minimal installation option.
- disable crashhandler by using "config set crashhandler false", this because the server will never really shut down properly and would trigger said crashhandler.
- enable local user accounts using "config set login true", chose your root password.
- install the server package using "mapt install netauth-server",
- launch the server using "nas start", you should see new tabs popping open.
- create a new user using "nas useradd admin password", change password with your password
- promote said user to admin/op using "nas op admin", you can now use this user to do admin tasks on the network.


3 - netauth-client
netauth client changes minux's login system to the network one, once set up it will use the server's user database and ignore the local one.
regular commands like "login" or "useradd" remain the same, you also gain "op" and "deop" as commands to promote and demote admins.
this works on basic and advanced computers.

- install the package using "mapt install netauth-client", the installer should pop up. (you can restart it any time using "/bin/netauth-client.sh")
- first provide the server's dns registered name (authserver), hit enter.
- provide your admin account's credentials, this is to ensure no unwanted systems get registered
- it will now look for the server and try to verify said credentials, it will tell you if it worked. if it failed no changes will be made to login.
- test your system by using "login admin password", it should switch to your new user. a restart at this point is advised.

4 - notes
- in case of emergency you can disable the login system by changing "login=false" to "login=true" in the file "/etc/minux-main/config/kernel.cfg" using a bootdisk.
- any minux program (eg "passdoor" or "netdoor" that uses the login functions from minux will also switch over to networked accounts.
- uninstalling netauth-client will reset minux's login system to disabled.
- you can restart netauth-client's installation tool using "/bin/netauth-client.sh"
- both the dns and auth servers need to be on a loaded chunk to respond to the client.
- you can create a closed network using network cables for additional security.
- both servers can make use of a large monitor to display messages to the admin without having to open the computers.