RustDesk package update [Solved]

[schwarzheit]

Rustdesk is currently installed in version 1.3.2 but there is already 1.4.

Can you please put the current version in repo?

[Eadwine Rose]

Moved to package requests forum

[dolphin_oracle]

rustdesk is not in our repos, and they do not provide a repo. you can re-run the mx-packageinstaller-popular-apps routine to get a new deb installed.

[schwarzheit]

Ah... Thanks.

I thought it would be updated automatically.

[Dearth]

You can also use deb-get:

https://github.com/wimpysworld/deb-get

RustDesk is available there and it will be updated automatically.

[dolphin_oracle]

You can also use deb-get:

https://github.com/wimpysworld/deb-get

RustDesk is available there and it will be updated automatically.

clarifying that it would be updated automatically by deb-get if you use deb-get for updates, not by the usual updater tools or any other package manager.

[kd4e]

Many have been suffering an odd failure of the OSS self host Server & are being told that they must install Docker in order to 'magically' fix the problem.
(Which means, of course, those people don't appear to understand how the code works.)

One use case is a Client & Server on the same LAN - with the Server on a Raspberry Pi.
(Docker is, clearly, not needed - or shouldn't be.)

This person explained what they've learned about Rustdesk and how they've solved the problems, despite the poor documentation:
https://www.reddit.com/r/rustdesk/comme ... ?context=3

If Rustdesk were to be added to the MX Linux repo - perhaps this could be included?

Also, myssv on github responded to my question about his 2023 update script:
"This is my update script and it is still working:"

Code: Select all

rm update.sh
wget https://raw.githubusercontent.com/techahold/rustdeskinstall/master/update.sh
chmod +x update.sh
./update.sh

HTH ...

[kd4e]

In a reddit thread about Rustdesk someone suggested this ...

Code: Select all

hbbs -r <comma,sep,list,of,URLs/IPs,where,client,could,reach,the,server> -R <the,same,list> -k "ThePrivateKeyHarvestedFrom-id_ed25519-AutoCreatedOnFirstRun"

And this

Code: Select all

hbbr -k "TheSamePrivKeyAsAbove 

and this

Code: Select all

export SINGLE_BANDWIDTH=256
export TOTAL_BANDWIDTH=2048
export LIMIT_SPEED=64
export ALWAYS_USE_RELAY=N
export ENCRYPTED_ONLY=1 

(He added this note "where their meaning is in the docs and largely understandable from the var name.")

Someone more familiar with the Rustdesk code would have to explain the how and why of all of that ...

[kd4e]

The same person just posted:

I've seen now that docs on these variables disappear from official docs, back then I've found in them. Their meaning is

SINGLE_BANDWIDTH=256 # in Mbps, max band of a single connecction
TOTAL_BANDWIDTH=2048 # max allowed band for all currently connected clients
LIMIT_SPEED=64 # file transfer max band per connection
ALWAYS_USE_RELAY=N # trying or not to go P2P
ENCRYPTED_ONLY=1 # allow (1) or not (0) unencrypted connections for clients with no/invalid public key configured
Evidently they try to discourage self-hosting now...

I'm now looking at https://ylianst.github.io/MeshCentral/meshcentral/ as an alternative to RustDesk.