Wyng for Noobs

Community Guides
61

My NAS is a Synology device, so not exactly that flexible. Assuming I can get some sort of Perl version installed then it would be an option. Synology Linux version is severely deprecated.

62

It does appear that perl 5.34 is available and can be added from the Synology Disc Station Manager: Perl - Add-on Packages | Synology Inc.

They also have a python 3.9 package (which I would expect to be much larger than perl so space on your system partition may be a concern): Synology Inc. Wyng can use python versions going back to 3.8.

1 Like
63

BTW… The Wyng v0.8.0 release is now out! :smiling_face:

2 Likes
64

I see the first 0.8 beta was tagged 2 years ago, you must be super happy to have a 0.8 release today. Let’s celebrate :partying_face: !

65

Yes. I should have made an incremental v0.4 release at that point instead of bumping the version way up. Lesson learned! :upside_down_face:

66

Great news! It’s really a tool that I really appreciate:D Tell me @tasket, there’s no need to use wyng-util-qubes anymore? Only wyng is enough? :slight_smile:

67

Testing of the new 0.8 release went well. Thanks for your efforts! As @Tezeria has mentioned, is the wyng-util-qubes wrapper still supported?

68

I cannot create an ssh backup. Are there settings in sshd or firewall (I blocked everything but tcp and the ip) that need to be set?
Normal ssh connections work, creating it without the wrapper also does not work

sudo wyng-util-qubes create --dest=qubes-ssh://wyng:user@1.1.1.1:200/mnt
Wyng-util-qubes v0.9 beta rel 20251105
Wyng 0.8.0 release 20251201

XXXXXXXXX)'.
mkdir -p -m 777 /tmp/wyngrpc/  && tdir=$(mktemp -d /tmp/wyngrpc/tmpXXXXXXXXXXXX)  && echo && echo $tdir && cat >$tdir/dest_helper.py
                                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
[0, 127]


StorageError: Destination not ready to receive commands.
69

Is your remote ssh user using bash? Same for the Qubes os side in the appvm. I had issues using fish.

1 Like
70

That was the issue. I also considered this because of the fish style error message but I did not change the shell of both ends…

71

This could be fixed with extra flags in wyng to configure the path of the shell to use on both ends. But it’s more work for @tasket unfortunately, it’s easier to change the shell at the moment :sweat_smile:

72

Some questions:

  • Can I use one wyng archive for multiple different qubes installs? Are there issues I will run into
  • How do you guys read a password from a file for the qubes wrapper --passcmd does not work. Is it okay to pipe like this cat pw | wyng or is this insecure / the password will be left somewhere