Skip to content

Commit 078571d

Browse files
authored
Merge pull request #1688 from cdr/fix-typos
Improve clarity in guide and fix typo in FAQ
2 parents f4c97ab + 25ea76e commit 078571d

File tree

2 files changed

+7
-5
lines changed

2 files changed

+7
-5
lines changed

doc/FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -108,7 +108,7 @@ only to HTTP requests.
108108
You can use [Let's Encrypt](https://letsencrypt.org/) to get an SSL certificate
109109
for free.
110110

111-
Again, Please follow [./guide.md](./guide.md) for our recommendations on setting up and using code-server.
111+
Again, please follow [./guide.md](./guide.md) for our recommendations on setting up and using code-server.
112112

113113
## How do I securely access web services?
114114

doc/guide.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -94,11 +94,13 @@ systemctl --user enable --now code-server
9494
**Never**, **ever** expose `code-server` directly to the internet without some form of authentication
9595
and encryption as someone can completely takeover your machine with the terminal.
9696

97-
There are several approaches to securely operating and exposing code-server.
98-
9997
By default, code-server will enable password authentication which will
100-
require you to copy the password from the code-server config file to login. You
101-
can also set a custom password with `$PASSWORD`.
98+
require you to copy the password from the code-server config file to login. Since it
99+
cannot use TLS by default, it will listen on `localhost` to avoid exposing itself
100+
to the world. This is fine for testing but will not work if you want to access `code-server`
101+
from a different machine.
102+
103+
There are several approaches to securely operating and exposing code-server.
102104

103105
**tip**: You can list the full set of code-server options with `code-server --help`
104106

0 commit comments

Comments
 (0)