[Ovmsdev] Enable/disable mode, and secure commands

[Mark Webb-Johnson]

We’ve implemented the ‘enable’ and ‘disable’ commands, and corresponding secure module for the consoles.

The module password is in:

Config
	Param:		password
	Instance:		module
	Value:		<plaintextpassword>

If there is no password defined (default case), you can just type ‘enable’ without password, and you’ll get into enable mode. Everything will be as it was before.

If a module password has been set, then you must type ‘enable <password>’ and the password must match, to enter enable mode. If the password you enter is wrong, then there will be a five second delay before you can try again (to limit brute force attacks).

The ‘disable’ command will switch back to insecure mode (the default), and some (most) commands will be restricted.

If there is no password/module defined, then the consoles will default to secure (enable) mode.

For example:

Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console

OVMS > vfs ls /store
Error: Secure command requires 'enable' mode

OVMS > enable <password>
Secure mode

OVMS > vfs ls /store
ovms_config
events

OVMS > disable

OVMS > vfs ls /store
Error: Secure command requires 'enable' mode

Regards, Mark.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20171014/9ceeb6b9/attachment.html>