Posted: Wed May 18, 2022 21:30 Post subject: [SOLVED]Your connection is not private
The DD-WRT "built-in" certificate from NewMedia-NET GmbH is not backed by a trusted cert authority so the browsers throw the annoying warning when opening the router's HTTPS web GUI. In OpenWRT I got rid of that by creating a self-signed certificate myself and uploading it into the /etc/ssl folder and the Windows cert stores. On DD-WRT that is not possible because the file system is read-only and chmod cannot change that (or I don't know how to change that).
I do understand that this is not a critical issue, it's my own LAN and I'm accessing it non-remotely and all that, but even if that is admittedly just a minor annoyance, I'd still be happy to get rid of it if there is a way. I did a lot of googling but did not manage to find a solution.
Can someone advise how to get rid of the annoying browser warning?
Last edited by Ivo_K on Thu May 19, 2022 22:19; edited 2 times in total
Thank you both for taking the time to respond to my question. I really appreciate it. In return - if you will allow it – I’ll take the liberty to offer back a bit of advice of my own that might be of benefit to other novices like myself when you answer their questions. So, here goes: while both of your responses were kind and useful, they were not really helpful. One was telling me to keep investigating because I have not done enough of it and the other was offering a very wise advice about the use of my time and telling me not to waste it on irrelevant issues such as the one at hand.
Dear Kernel-panic69, this is indeed a question that has been asked an awful lot of times and there is a plethora of information about the topic available on the Web (I have done a lot of investigation before posting here, despite your conclusion to the contrary). But perhaps that very fact is an indication that there might be something lacking in that information which then makes people ask it again and again. An unfortunate lack of information, mind you, not lack of people’s diligence or willingness to investigate on their own.
Dear Joker, yours is indeed an extremely wise message albeit somewhat misplaced. I have noticed that you are very active on this forum and in fact you have also kindly answered some of my previous questions for which I am immensely grateful. I would however never dream of telling you that maybe you should use your time more wisely instead of squandering it in this forum. We know nothing about each other’s respective motivations or each other’s eventual objective limitations when it comes to the time spending choices we have at our disposal.
My kind suggestion to both of you: if you can help by answering the question somebody poses here, please do so with patience and kindness. Otherwise just ignore it. We who ask questions do so because we need help with our DD-WRT and have exhausted our own (sometimes very limited) resources. We do not come here for admonishment or life wisdom.
BTW, I have managed to solve the problem, following the instructions in https://gist.github.com/alexandrusavin/69b26846d6593d6f217219b5bd8882c4, which Kernel-panic69 also mentioned. I had already seen that article before, but the one bit missing there which I wasn’t able to understand until just now when I had a sudden epiphany, was that in order for the jffs folder to be created and mounted you also had to mark Clean Internal Flash Storage in the web GUI and then reboot the router after applying these changes. Now I’m a happy camper with no annoying browser messages.
Joined: 08 May 2018 Posts: 13885 Location: Texas, USA
Posted: Thu May 19, 2022 22:49 Post subject:
Ivo_K wrote:
Dear Kernel-panic69, this is indeed a question that has been asked an awful lot of times and there is a plethora of information about the topic available on the Web (I have done a lot of investigation before posting here, despite your conclusion to the contrary). But perhaps that very fact is an indication that there might be something lacking in that information which then makes people ask it again and again. An unfortunate lack of information, mind you, not lack of people’s diligence or willingness to investigate on their own.
See below. That link was the 3rd listed in my search results. Sorry if my brevity wasn't coloring outside the lines or kindler and gentler enough.
Ivo_K wrote:
BTW, I have managed to solve the problem, following the instructions in https://gist.github.com/alexandrusavin/69b26846d6593d6f217219b5bd8882c4, which Kernel-panic69 also mentioned. I had already seen that article before, but the one bit missing there which I wasn’t able to understand until just now when I had a sudden epiphany, was that in order for the jffs folder to be created and mounted you also had to mark Clean Internal Flash Storage in the web GUI and then reboot the router after applying these changes. Now I’m a happy camper with no annoying browser messages.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Thu May 19, 2022 23:15 Post subject:
Your long message makes little sense and its contradictory as a whole. We were kind and helpful but not useful and then it turns out we were none of the above and not even patient.
And you managed to solve the issue with one of the replies contents, so it was helpful after all. mmmm
I just think to myself, this is a perfect example of how it is impossible to please everyone all the time. But do enjoy the free firmware and support and you're welcome for the misplaced advice.
None of us get paid for any of the countless hours we all put into DD-WRT be it by providing support, making patches for it and generally finding out we fall way short of some intangible expectation.
If any part of my "long message" was understood as offensive or ungrateful, please accept my sincere apologies. That was definitely not even the remotest intention when I wrote it, please rest assured.
My point was that even when you are - as is definitely the case here - kind and helpful, the original problem may finally remain unsolved and hence your advice not really helpful. In this case what finally solved the problem was not the quoted article. Following the instructions there one will reach an error:
sh: 2228: unknown operand
mount: mounting /jffs/etc/privkey.pem on /etc/privkey.pem failed: No such file or directory``
In order for this procedure to work, the jffs directory needs to be "formatted" and for that to happen you also need to mark Clean Internal Flash Storage in the web GUI after step 1.iii and then reboot the router after applying these changes. And this is not mentioned in the instruction. Probably this is expected to be known by the more savvy readers but in my ignorance I did not do so and therefore was at a loss as to how to proceed. I have later discovered the missing step by pure accident.
Once again, many thanks for your kind support anyway. No hard feelings, I hope.
Joined: 08 May 2018 Posts: 13885 Location: Texas, USA
Posted: Fri May 20, 2022 1:17 Post subject:
No hard feelings here. I wasn't trying to take your response the wrong way, it just felt like as much as I was trying to at least give you some information to read that I felt might be helpful, I was getting the stink eye, lol. I think the JFFS thing is a 'universally known, unwritten rule' perhaps (but I think it does mention it somewhere in the wikis...) and sometimes people just don't realize that there is a proper order of operations / procedure and it can be a frustrating pain in the ass. Glad you got it sorted. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sat May 21, 2022 13:02 Post subject:
Murphy's law applies to this thread.
It could have ended with a simple thanks and notes on the findings, now its just useful lost information in a sea of noise.
P.S. I had half a mind of editing out the noise, so that the helpful parts would prevail, instead it shall remain a reminder of the pop-corn moment it turned out to be.
Locking for a cooldown period, shall be unlocked again when such arbitrary time has passed.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Tue May 24, 2022 9:47 Post subject:
Unlocked, now keep in mind the forum rules when posting any further comments. Try to keep any replies ontopic for the issue/solution and use constructive ways to suggest improvements to documentation.
