Fix deCONZ issue with old vnc access (#1513)

This commit is contained in:
Pascal Vizeli
2020-07-28 19:38:39 +02:00
committed by GitHub
parent 5ec3867b18
commit 0cf3ae0795
3 changed files with 8 additions and 2 deletions

View File

@@ -1,5 +1,9 @@
# Changelog
## 6.2.1
- Fix old fashon VNC access
## 6.2.0
- Enable VNC per default

View File

@@ -1,6 +1,6 @@
{
"name": "deCONZ",
"version": "6.2.0",
"version": "6.2.1",
"slug": "deconz",
"description": "Control a Zigbee network with ConBee or RaspBee by Dresden Elektronik",
"arch": ["amd64", "armhf", "aarch64"],
@@ -19,7 +19,7 @@
"40850/tcp": null
},
"ports_description": {
"5900/tcp": "deCONZ desktop via VNC (Not required for Ingress)",
"5900/tcp": "deCONZ via VNC (Not required for Ingress. Not secure!)",
"8081/tcp": "deCONZ WebSocket (Not required for Ingress)",
"40850/tcp": "deCONZ API backend (Not required for Ingress)"
},

View File

@@ -42,6 +42,7 @@ fi
# Run it only on localhost if not expose
if bashio::var.has_value "${VNC_PORT}"; then
bashio::log.warning "Your direct VNC access is not protected!"
LOCAL_ONLY=no
else
LOCAL_ONLY=yes
@@ -57,6 +58,7 @@ tigervncserver \
-depth 16 \
-localhost ${LOCAL_ONLY} \
-SecurityTypes None \
--I-KNOW-THIS-IS-INSECURE \
"${DISPLAY}" \
&> /dev/null