RPJosh
/
wayvnc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix typos in README.md

pull/118/head
Matthias Braun 2021-11-01 11:33:25 +01:00 committed by Andri Yngvason
parent 7581cf0bc4
commit 8a65a8557e
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@ -1,8 +1,8 @@
# wayvnc # wayvnc
## Introduction ## Introduction
This is a VNC server for wlroots based Wayland compositors. It attaches to a This is a VNC server for wlroots-based Wayland compositors. It attaches to a
running Wayland session, creates virtual input devices and exposes a single running Wayland session, creates virtual input devices, and exposes a single
display via the RFB protocol. The Wayland session may be a headless one, so it display via the RFB protocol. The Wayland session may be a headless one, so it
is also possible to run wayvnc without a physical display attached. is also possible to run wayvnc without a physical display attached.
@ -13,7 +13,7 @@ project.
## Installing ## Installing
``` ```
# archlinux # Arch Linux
pacman -S wayvnc pacman -S wayvnc
# FreeBSD # FreeBSD
@ -45,12 +45,12 @@ xbps-install wayvnc
* ninja * ninja
* pkg-config * pkg-config
#### For archlinux #### For Arch Linux
``` ```
pacman -S base-devel libglvnd libxkbcommon pixman gnutls pacman -S base-devel libglvnd libxkbcommon pixman gnutls
``` ```
#### For fedora 31 #### For Fedora 31
``` ```
dnf install -y meson gcc ninja-build pkg-config egl-wayland egl-wayland-devel \ dnf install -y meson gcc ninja-build pkg-config egl-wayland egl-wayland-devel \
mesa-libEGL-devel mesa-libEGL libwayland-egl libglvnd-devel \ mesa-libEGL-devel mesa-libEGL libwayland-egl libglvnd-devel \
@ -96,10 +96,10 @@ accept connections via any interface, set the address to `0.0.0.0` like this:
:warning: Do not do this on a public network or the internet without :warning: Do not do this on a public network or the internet without
user authentication enabled. The best way to protect your VNC connection is to user authentication enabled. The best way to protect your VNC connection is to
use SSH tunneling while listening on localhost, but users can also be use SSH tunneling while listening on localhost, but users can also be
authenticated when connecting to Wayvnc. authenticated when connecting to wayvnc.
### Encryption & Authentication ### Encryption & Authentication
You'll need a private X509 key and a certificate. A self signed key with a You'll need a private X509 key and a certificate. A self-signed key with a
certificate can be generated like so: certificate can be generated like so:
``` ```
openssl req -x509 -newkey rsa:4096 -sha256 -days 3650 -nodes \ openssl req -x509 -newkey rsa:4096 -sha256 -days 3650 -nodes \