For the more normal users it can be an issue. It is targeted at the single usage regular crowd, who have an internet connection on the machine they create the USB on.įYI, most power users and sysadmins are able to do tethering with their phones so it's not like this is a major issue for them (that's how I worked around the issue when in the field). If you drop the code dealing with this download-on-demand, you can even have less stuff to maintain, win-win. This can be done with a 2-line bash server-side script, and will require 0 mainteneance on your side.
![rufus syslinux 6.03 download rufus syslinux 6.03 download](https://www.german-syslinux-blog.de/wp-content/uploads/2018/05/WSUS-Offline_Update_Generator.png)
You can just bundle all files (rufus executable and these additional files already in the folder) in a single zip that is downloaded together by the user himself, instead of having the user download only rufus, and then have rufus download stuff on demand. That's beyond overkill, I wasn't asking for that. You need to keep both your browser and your OS up to date.I'd have to add and maintain a web crawler a la HTTrack in Rufus Updating your browser alone is not enough. I'd much rather continue to educate people that keeping their OS up to date is not something that they should ever consider as optional (so that they can avoid the pain of malware that exploits vulnerabilities that have been patched) than foster the idea that using a non up to date OS is okay, and that software like Rufus should help users who choose to run their OS in such a manner. If you have an example of a vanilla Windows 7 system, where all the updates have been applied, that can't access a modern SSL website, I'll be happy to hear it, because I did test that a vanilla Windows 7, with all updates applied, could access GitHub in SSL mode (where the files are being served) be it from Rufus or Internet Explorer.Īnd no, as I explained at length in the issues you linked, I'm not going to add a custom multi MB SSL library so that users of an OS that is going to become obsolete in 2 months can spare themselves the trouble of keeping it up to date, or even an additional warning besides the one they get from the log. Please try to access the files with Internet Explorer, you will see.Īnd I will also encourage you to read through the issues you linked, where I pretty much explain the same thing. As I explained, it's not because browsers, that use their own internal SSL library, can access a modern SSL website that an OS that hasn't been updated will. I am talking about making sure that you have applied all the Windows 7 updates that are published by Microsoft as some of those are important if you do want to access SSL websites). If "users shouldnt have to rely on rufus to get these files" then I will posit that "users should keep their OS fully up to date" instead of expecting applications like Rufus to work around an issue that only exists due to users choosing to use a non up to date OS (and no, I am not talking about upgrading from Windows 7 to Windows 10. However, considering what I explained above, I hope you can appreciate that the issue is far from being the generalized problem that you may imagine it is, but instead is restricted to a minority of Windows 7 users.Īs such it makes little sense to take additional steps besides notifying the users that they should keep their OS up to date, because that is really the core of the issue. As opposed to browsers that use their own custom SSL libraries, and therefore manage to access modern version of SSL secured servers such as GitHub, Rufus relies on the Windows networking libraries, and, if you happen to be running on Windows 7, an OS that is going to be obsoleted in about two months, and you haven't applied all the system updates (because if you do, then the system SSL libraries will be updated and allow you to access GitHub) then you will face the issue you described above.