Hi Chris, We've started to use an HTTPS link on port 4201. The usual 4200 port is automatically redirected as well. The self-signed certificate warning is a temporary evil to protect a new token requested for access control.
We are working on additional security parts for snapweb, like SSO/macaroon authentication in particular, to improve the usability. If something is unclear, please help us document it by filing a bug at: https://bugs.launchpad.net/snapweb/+filebug Thanks On Tue, Oct 25, 2016 at 2:26 AM, Chris <cpoll...@embarqmail.com> wrote: > This is the first time I've noticed this happening and I keep SnapWeb > loaded in my browser. > > The owner of localhost has configured their website improperly. To > protect your information from being stolen, Firefox has not connected > to this website. > > localhost:4201 uses an invalid security certificate. The certificate is > not trusted because it is self-signed. The certificate is only valid > for 127.0.0.1 > > But, is the error caused by a setting I have not correct? > > Chris > > -- > Chris > KeyID 0xE372A7DA98E6705C > 31.11972; -97.90167 (Elev. 1092 ft) > 19:21:04 up 4 days, 10:45, 1 user, load average: 0.73, 0.31, 0.20 > Ubuntu 16.04.1 LTS, kernel 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 > 14:12:37 UTC 2016 > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > >
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
