Since the new firmware all files and the directory with the name update are deleted after 24 hours.
Is this a bug or intend to work this way?
First I though I had a bug in my script: https://github.com/wbartels/IPSet_ASUS_Lite/issues/2
But even a directory outside skynet was deleted after 24...
For your information
The blocklist.de website seems to be down.
https://iplists.firehol.org/files/blocklist_de.ipset serves an older version.
Witch is an importend part of firehol_level2
I hope it will be back shortly ;)
openssl does not use the standard base64 encoding and decoding without the -A option:
https://stackoverflow.com/a/35296674/7484547
With the examples below, you see that without the padding the last character is missing.
In your case padding is not strict required.
Without padding
#!/bin/sh...
Your code is missing the trailing padding.
Here is a way to reconstruct the padding (converted from the previous posted PHP code):
hash='12345'
echo -n "$hash"; echo '====' | cut -c-$(($(echo -n "$hash" | wc -m) % 4))
skynet@RT-AX88U-DC28:/tmp/home/root# echo "AgMAAAAAAAAADzE0OS4xNTQuMTUzLjE1MyA-GhoPbFPz6XpJLVcIS1uYBwWe4FerFQWHb9g_2j24OBhhZGZyZWUudXNhYmxlcHJpdmFjeS5uZXQKL2Rucy1xdWVyeQ" | openssl enc -a -d
skynet@RT-AX88U-DC28:/tmp/home/root#
This is not standard Base64, but URL safe Base64, encoding is...
Thanks! Can the “certificate is expired” only be the server certificaat? I ask this because the same url is working perfectly on Ubuntu 18.04 with curl. See https://www.snbforums.com/threads/384-17-curl-60-ssl-certificate-problem-certificate-has-expired.64455/
Since today I get the "curl: (60) SSL certificate problem: certificate has expired" error on one site:
# curl -v https://www.myip.ms/files/blacklist/csf/latest_blacklist.txt
* Trying 2607:5300:60:8137:a149::1:443...
* Immediate connect fail for 2607:5300:60:8137:a149::1: Network is unreachable...
Many scripts use curl to download none binary files.
To reduce unneeded bandwidth it would be nice if curl can support deflate and gzip decompression.
At the moment it is not supported:
# curl --compressed -o /dev/null https://iplists.firehol.org/files/greensnow.ipset
curl: option --compressed...
The purpose of Skynet-Whitelist, Skynet-Blacklist and Skynet-BlockedRanges are clear. But how do the Skynet-IOT work. Why do the IOT (internet of things) need other rules? Thanks Willem
It took me some time. But now I have a working version.
See github for more info: https://github.com/Adamm00/IPSet_ASUS/issues/27
This proof of concept will demonstrate two new features:
Only download new or changes ipsets (already implemented in Skynet 7)
Only update new or changed ipsets...