You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a way to implement security for the server? I need it to only be accessable with a password, as my WiFi network is not secure (I am doing this at a university).
The text was updated successfully, but these errors were encountered:
You'd have to perhaps do something like IP address filtering at your
network level on your computer to limit it. The notion is that you'd solve
authentication at a router/firewall layer instead of in SPJS. You could
possibly add a command line switch and pass in an IP address filter list
too. You could possibly also change the websocket URL from the /ws to some
kind of password like path but you'd have to do that as a command line
switch too. Changing all the UI out there to support password would be hard.
On Thu, Jun 21, 2018 at 9:08 AM feistjo ***@***.***> wrote:
Is there a way to implement security for the server? I need it to only be
accessable with a password, as my WiFi network is not secure (I am doing
this at a university).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#54>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHidbYN1hljn_frVJCDNhHWeNhzObBr5ks5t-8UWgaJpZM4UyXO0>
.
Is there a way to implement security for the server? I need it to only be accessable with a password, as my WiFi network is not secure (I am doing this at a university).
The text was updated successfully, but these errors were encountered: