Recent content by RMerlin

Any feedback on the (albeit obscure) static key auth method? I already removed it from the server code, I am debating removing it from the client code as well considering how obscure (and much less secure than regular tls auth) it is. Personmally, I don't remember having ever seen it deployed.

All tunnel providers should have disabled compression many years ago. My concern is more for the server config, where some people might have enabled it for remote access without being aware of the feature deprecation. But I think that if it gets documented in the changelog, they will have...

That`s not a kernel panic, that`s just an application crash. A kernel panic is like a BSOD on Windows - it causes the entire system to crash and require a reboot.

asd is an Asus service, not a TrendMicro service. As your second crash, it's the networkmap service that crashed.

With stock firmware they are directly downloaded from Asus' website every time you access this page. For Asuswrt-Merlin I chose to keep local copies of all these files within the router itself, so routers won't need to constantly connect with Asus's website. So all I do is I regularly download...

I have started working on OpenVPN 2.7 support, and am reviewing some of the changes that came with it. Two important things: --secret support is now disabled by default. That authentication method is deemed no longer safe, so by default OpenVPN no longer supports it. Unless I can get a good...

Manufacturing hardware in the US has nothing to do with software-related flaws and won't change anything there. Also, Code Red and Nimda still happened despite Windows being developped in the USA.

My guess is that Asus might have goofed at one point and pushed a signature with the wrong version number. Worst case scenario, people could probably delete the signature files saved to /jffs, then force an update.

This is more about his multiple threats that were made against broadcasters than the current router issues tho.

Probably because nobody even knows for sure what is going to happen with yet-to-be-validated products. This is yet another very vague claim from the US administration that "we will do <insert something that wasn't fully thought of>", and everyone now has to wait for concrete plans to be...

Thanks. So what this tells is is the disk does register as roughly 64 GB, but you have two partitions that only take up a few megabytes each. I'll leave it to OpenWRT experts to guide you beyond that.

Gl.INet statement: https://www.gl-inet.com/blog/glinet-statement-on-recent-fcc-regulatory-developments/

We'd need to see the total block count shown above, to determine how much of it is actually used by the existing partitions.

Check the partition table. fdisk -l /dev/mmcblk0

SQ is for test purposes (Software Qualification or something like that).