MichaIng

@djmdjm Can you give us an advice how to achieve that? Read what I said above that there is no way to send a PR or issue to Phil's repo...

Since OpenWRT is a single-user single-purpose distribution, there is no problem with them changing default paths or configs as they like. However, when developers of unrelated software start to adapt...

> detect the presence of OpenWRT through some other way If someone knows a failsafe (!) way to do so, I'm open to edit the PR accordingly. However, removing it...

Checking for `/etc/openwrt_release` existence seems to be best/safest. To assure the change is as targeted as possible, wouldn't it make sense to leave `INSTALLKEYS_SH` as it is unless the remote...

> Good point, although user only matters on the server side. The user name is the same on server and client, so this can be known before even connecting to...

> Not necessarily. It can be set in the config file or on the ssh-copy-id command line option. I have to look into the code, but within `ssh-copy-id` surely there...

Great news, many thanks for taking care of this 👍. Still, some concerns about the implementation: ```sh [ -f /etc/openwrt_release ] && [ "\$LOGNAME" = "root" ] && AUTH_KEY_FILE=/etc/dropbear/authorized_keys; ```...

I'm working on it, i.e. the PyPI upload along with a pre-release tag here on GitHub: #2675

Has anyone time and mood to wrap up some release notes for 0.43.0 (or 0.43.1, possibly technically required)? Aside of Python 3 migration, lots of other features and fixes have...

At least for this release this would be really messy, due to quite some back and forth and non-linear merges, also from the previously dedicated l18n/i10n project. But for the...