Ok, you guys are right, we should focus on updating and then fixing the issues we have, I agree let's put the firmware downgrade aside.
The first is updating across multiple versions.
Then how to protect the admin password?
@ExtremeFiretop @dave14305
I rule them out. People who are on older than N-1 firmware probably aren’t interested in (or going to be aware of) an auto-upgrade add-on.
Hey team!
Sorry for the delay, work was nuts today!
I fully agree with this by dave. Once they’re current via other means, they would stay current with each incremental firmware release of our script.
I don't know many people going out of their way to setup a router without first updating it, however we can try to implement as many safeties as possible, (such as a hard min version)
but look, at the end of the day, an update is always the responsibility of the user.
I am not sure how many times we've said this, but naturally if your service is *relying* on some shacks VPN connection out in the woods, then maybe auto update isn't for you, no problem, no one is forced to use it.
I expect people to display some understanding of the risks involved with your network and decide accordingly. Same as stock firmware with it being enabled or disabled.
Simply giving the users the option is not enough of a reason for me not to be interested.
I can guarantee my home service is not so sensitives as a banks, etc, and I have the confidence that if I initiate a firmware update over the web GUI, for a single version increase, it should be fine 98% of the time.
These hypotheticals where a company like SourceForge is hijacked is nice to think about, and develop some understanding of the risks before moving forwards is required!.
But if that really happened and someone came to me complaining, I would simply laugh. How is SourceForge being hihacked my problem?
It really isn't, using my script or not, if it was hijacked you likely downloaded (automatically or manually) compromised firmware. As long as it's offered on SourceForge, that risk has already been calculated in the project.
As already discussed a delayed release cycle will help combat this situation.
EDIT:
Another solution is to work with you (
@RMerlin ). When you decide that it is not appropriate to automatically update a firmware version, you add a fixed-format message to the changelog.
for example:
Code:
386.11 (14-May-2023)
[Auto Update: this version requires user confirmation]
- UPDATED: curl to 8.0.1.
- UPDATED: openvpn to 2.6.3.
- CHANGED: Reduce max OpenVPN clients to 2 for RT-AC68U and
DSL-AC68U due to lack of NVRAM on these two
models. Note that existing settings are not
automatically removed, you must run the following
command over SSH to remove them from nvram and
the /jffs/openvpn/ directory:
clear_vpnclients.sh
A backup will be saved in /jffs/openvpn_backup.tgz.
- FIXED: DDNS was being refreshed every time IPv6 bound6() event
occured even if IPv6 DDNS update was disabled.
- FIXED: Wireless Log wouldn't properly show IPv6 address
for clients with multiple addresses.
- FIXED: dnsmasq may crash if no DNS server is configured
(fix backported from dnsmasq upstream)
The automatic update script will not automatically update after matching the content (
[Auto Update: this version requires user confirmation]
). Instead, as I mentioned before, it will trigger a notification that requires user intervention.
I like the sentiment, but I wouldn't have even asked, clearly if merlin had interest in auto update he would of done it himself or displayed interest in the project once we got it working through Web UI.
This really is going to be a fun project of troubleshooting our way through most of the steps, including this one.
Can’t we just hack along and see how far we get before deciding we have to account for every corner case and remote router in a cabin in the deep woods?
Love it! On the same page! Move on
The point at the end of the day is if we can get this to work reliability.
Something I or you can use personally at home, where I can trust 98% of the time it will be fine, and the 2% where something could potentially happen (such as hijacked SourceForge or a bad/broken Final release)
I will have a USB with backup tools to restore quickly and effectively, and that still cuts down my human interaction by most of the time.
I did make note though of some needed hard coded min version.