Skip to content
This repository has been archived by the owner on Sep 27, 2020. It is now read-only.

Enable the "visitor" mode #23

Open
digitalLumberjack opened this issue Sep 21, 2015 · 4 comments
Open

Enable the "visitor" mode #23

digitalLumberjack opened this issue Sep 21, 2015 · 4 comments
Labels

Comments

@digitalLumberjack
Copy link
Member

Allow other users to connect the manager throught a visitor mode.
The means to add some sort of authentication.

@sveetch
Copy link
Member

sveetch commented Sep 21, 2015

Well there is two things in you issue.

  • Enable authentification. This is either with the Django session/auth or either a webserver auth (like with htacess). The first one can be enabled easily, but i planned to totally remove the session/auth to totally avoid database usage, to enlight cpu/memory usage. The other is for "real" webserver, like Apache/lhttpd/nginx/etc.. but actually we don't have one (again to save memory/cpu usage).
  • Visitor mode. Depend on choice for the previous part.

Frankly, for the first release i thought we don't really have to bother on these things.

@digitalLumberjack
Copy link
Member Author

I was not thinking about the first release. Just an idea

Le lun. 21 sept. 2015 à 13:39, David THENON notifications@github.com a
écrit :

Well there is two things in you issue.

Enable authentification. This is either with the Django session/auth
or either a webserver auth (like with htacess). The first one can be
enabled easily, but i planned to totally remove the session/auth to totally
avoid database usage, to enlight cpu/memory usage. The other is for "real"
webserver, like Apache/lhttpd/nginx/etc.. but actually we don't have one
(again to save memory/cpu usage).

Visitor mode. Depend on choice for the previous part.

Frankly, for the first release i thought we don't really have to bother on
these things.


Reply to this email directly or view it on GitHub
#23 (comment)
.

@MaxCorpEnjoy
Copy link

Adding some sort of authentification should be a requirement if you are not alone on your LAN, or if, for some reason, you want to access your recalbox from the internet.
So it would be good if there was a variable somewhere in the recalbox to :

  • either enabling/disabling the whole interface
  • or enabling/disabling authentification (and setting the password)

@sveetch
Copy link
Member

sveetch commented Dec 18, 2015

If we "secure" the manager interface it wont be a switchable feature, because the machinery need for authentication is too complex to implement it as a conditional feature and will require too many time to build and manage.

I'm agree about authentication requirement for non private LAN, it's just on raspberry we are somewhat restrained on ressources, but enabling will take some more ressources in the django instance.

The recalbox team should validate than the manager can take some more ressources on system, so i will be more confident about enabling authentication. Itself the authentication is pretty easy to enable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants