dyndns/users/example.yml

username: example
password: $2a$10$ymHFfGjKINWsUKwEo5xp.efN6DR6NkiRCXsbH4VWo0Nnzma8Yc.82
domain: dyn.local
router: 
  Hostname: mainhost
  NFT:
    table: sshguard
    set4: blackhole
    set6: blackhole6
others:
  - Hostname: atlantis
    v6iid: ::dead:beef:dead:beef
    registerv4: true
    NFT: 
      table: sshguard
      set4: blackhole
      set6: blackhole6
  - Hostname: troya
    v6iid: ::cafe:babe:deca:fbad
    registerv4: false
    NFT:
      table: sshguard
      set6: blackhole6
Added state perstistance - Define new state directory to hold the last dns update config and push it into the config, default to state/ - Refactoring, move updaterequest into service and out of webapp. Keep only the form parsing there. Specifically, move the processing code into the service package, it shouldn't be in the webapp. - Add code to load and save the last updaterequest into a state file (watch out to keep the possibly unhashed password out of it). - Add a command line option to load all available state files given the current configured user list from the command line. - Refactor user configuartion loading to separate it from user authentication, claen up the code. - We now require the username in the config, to make handling it in state updates easier. This will allow easier transition to DB style storage anyway. - Update .gitignore 2021-09-18 13:38:49 +00:00			`username: example`
- Clarified web handler name - Implemented Configuration Loader with unauthorized error handling - More elaborate test user config - Use Viper Unmarshalling for User Config loading - Centralized password hasing code 2021-08-22 12:36:55 +00:00			`password: $2a$10$ymHFfGjKINWsUKwEo5xp.efN6DR6NkiRCXsbH4VWo0Nnzma8Yc.82`
First working implementation - implemented update request processing - separated host and domain name in config (req. for DNS updates) - enhanced NFT update validation - cleaned up example user - cleand up logging in update request - moved appropriate config into user request struct 2021-08-24 14:44:52 +00:00			`domain: dyn.local`
- Clarified web handler name - Implemented Configuration Loader with unauthorized error handling - More elaborate test user config - Use Viper Unmarshalling for User Config loading - Centralized password hasing code 2021-08-22 12:36:55 +00:00			`router:`
First working implementation - implemented update request processing - separated host and domain name in config (req. for DNS updates) - enhanced NFT update validation - cleaned up example user - cleand up logging in update request - moved appropriate config into user request struct 2021-08-24 14:44:52 +00:00			`Hostname: mainhost`
Refactorization and further implementation - renamed clientoinfo to updaterequest - added userconfig skeleton - added hashed password skeleton 2021-08-21 18:34:45 +00:00			`NFT:`
			`table: sshguard`
			`set4: blackhole`
			`set6: blackhole6`
			`others:`
First working implementation - implemented update request processing - separated host and domain name in config (req. for DNS updates) - enhanced NFT update validation - cleaned up example user - cleand up logging in update request - moved appropriate config into user request struct 2021-08-24 14:44:52 +00:00			`- Hostname: atlantis`
Refactorization and further implementation - renamed clientoinfo to updaterequest - added userconfig skeleton - added hashed password skeleton 2021-08-21 18:34:45 +00:00			`v6iid: ::dead:beef:dead:beef`
- Clarified web handler name - Implemented Configuration Loader with unauthorized error handling - More elaborate test user config - Use Viper Unmarshalling for User Config loading - Centralized password hasing code 2021-08-22 12:36:55 +00:00			`registerv4: true`
Refactorization and further implementation - renamed clientoinfo to updaterequest - added userconfig skeleton - added hashed password skeleton 2021-08-21 18:34:45 +00:00			`NFT:`
			`table: sshguard`
			`set4: blackhole`
- Clarified web handler name - Implemented Configuration Loader with unauthorized error handling - More elaborate test user config - Use Viper Unmarshalling for User Config loading - Centralized password hasing code 2021-08-22 12:36:55 +00:00			`set6: blackhole6`
First working implementation - implemented update request processing - separated host and domain name in config (req. for DNS updates) - enhanced NFT update validation - cleaned up example user - cleand up logging in update request - moved appropriate config into user request struct 2021-08-24 14:44:52 +00:00			`- Hostname: troya`
- Clarified web handler name - Implemented Configuration Loader with unauthorized error handling - More elaborate test user config - Use Viper Unmarshalling for User Config loading - Centralized password hasing code 2021-08-22 12:36:55 +00:00			`v6iid: ::cafe:babe:deca:fbad`
			`registerv4: false`
			`NFT:`
			`table: sshguard`
Added state perstistance - Define new state directory to hold the last dns update config and push it into the config, default to state/ - Refactoring, move updaterequest into service and out of webapp. Keep only the form parsing there. Specifically, move the processing code into the service package, it shouldn't be in the webapp. - Add code to load and save the last updaterequest into a state file (watch out to keep the possibly unhashed password out of it). - Add a command line option to load all available state files given the current configured user list from the command line. - Refactor user configuartion loading to separate it from user authentication, claen up the code. - We now require the username in the config, to make handling it in state updates easier. This will allow easier transition to DB style storage anyway. - Update .gitignore 2021-09-18 13:38:49 +00:00			`set6: blackhole6`