User Details
- User Since
- Aug 20 2020, 9:55 AM (222 w, 2 d)
Oct 19 2024
Jul 1 2024
May 23 2024
The idea is feasible for parameters with constraints (like number ranges) defined in the XML, but there are many other cases where human input is necessary. We could give the tool a set of parameters to randomly generate, or a half-complete config with slots to fill in with random values. Worst case, we'd discover new constraints for more rigid templates; best case, we'd have a proper tool for generating corner cases for smoke tests and fuzzing.
May 16 2024
Feb 8 2024
Jan 25 2024
Jan 18 2024
After some research, I have concluded that the error was caused by the string's violation of RFC 3986, which recommends using percent encoding instead. I'll look into the feasibility of implementing percent encoding/decoding (which urllib natively supports) for spicy characters if there's demand, but the recommended method in VyOS right now is using the protocol-agnostic REMOTE_USERNAME and REMOTE_PASSWORD environment variables, which bypass the URL decoding step. The alternative would involve messing with urllib.parse's internal parser to implement a laxer and less greedy regexp to accept passwords like this, which is probably a bad idea.
Jan 4 2024
T4516 adds this functionality.
Dec 28 2023
@trae32566 Are you experiencing this with the latest rolling version? 1.5-rolling-202312130023 was released mere hours before the fix was pushed. See also: T5774
Nov 26 2023
Nov 25 2023
KeyboardInterrupt is caught with an appropriate error message now.
Nov 22 2023
Nov 15 2023
Oct 26 2023
Oops, wrong task.
Oct 19 2023
Oct 14 2023
Oct 12 2023
Oct 6 2023
Oct 1 2023
Sep 28 2023
show-dhcp-leases.pl under vyatta-op remains the only extant deadweight Vyatta script and needs to be removed.
Jun 10 2023
Apr 17 2023
Mar 9 2023
Mar 2 2023
Jan 26 2023
Jan 24 2023
Jan 20 2023
If the script returns nothing, the raw mode returns "". Is this expected behaviour? Should it not be {}?
Jan 18 2023
Removing the deprecation notice from 1.4.
Jun 2 2022
Apr 14 2022
This seems to be Cloudflare's doing, not ours. We're investigating this issue.
Mar 24 2022
Mar 16 2022
Note: Equuleus still uses the C preprocessor. // substrings (otherwise interpreted as comments) were escaped as \/\/ in op-mode-definitions/generate-public-key-command.xml.in in Equuleus and should be converted back eventually.
Mar 10 2022
I'm going to be experimenting with Jinja 2 to see if we can incorporate it into our template processor.
Actually, let's leave it in 1.3 but backport the warning and generate public-key-command.
Mar 8 2022
I'm removing loadkey from 1.4. It will be removed from 1.3.1, as well. Eventually, the warning will be dropped from 1.4 but it will remain in 1.3.
Mar 3 2022
Feb 11 2022
Jan 11 2022
Chained exceptions are covered too (and backported to Equuleus).
Jan 10 2022
Pythonic reimplementation complete. Now only the XML op-mode definition and the auto-complete script remain.
Jan 9 2022
Some notes:
- The old syntax is quite terrible. It breaks if an image is named disk-install or running or any remote protocol. There needs to be a cleaner syntax for it, such as copy file from image My-Image/usr/local/foo to path /tmp/foo or show file in remote ftp://ftp.example.net/foo.
- 'Image tools' isn't exactly a descriptive name for it. It does four operations:
- show: List files in a directory, or spit information about a file followed by its contents (hexdump if it's binary).
- copy: Copy a file or directory from one place to another (it can merge directories).
- delete: Deletes a file or directory (doesn't work remotely).
- update and updateone: Updates an image's config directory with rsync (the only part directly related to image manipulation). This is actually called clone in the CLI.
- show, copy and delete should probably be moved to a separate (new) module related to file operations (and coupled with vyos.remote) whilst update needs to become its own thing (a helper script, perhaps).