[22:40:00] Site:14qzPj..xnfZ content.json: verify sign error: VerifyError: Content too large 61028373B > 20971520B, aborting task... in ContentManager.py line 925 > ContentManager.py line 806
[22:40:09] Site:14qzPj..xnfZ content.json: verify sign error: VerifyError: Content too large 61028373B > 20971520B, aborting task... in ContentManager.py line 925 > ContentManager.py line 806
[22:41:13] Site:185yXN..mecL data/users/14dSDrqqtK4yG9LnbiWvVEECfLAUGtz8yN/content.json: verify sign error: VerifyError: Invalid cert signer: kxoid.bit in ContentManager.py line 913 > ContentManager.py line 758
[22:43:25] Site:1Music..icpB data/users/1GVM7nNzmYJ3ppPCmDTPLozrJF2Z9mgFpF/content.json: verify sign error: TypeError: 'NoneType' object is not iterable in ContentManager.py line 927 > CryptBitcoin.py line 75 > BitcoinECC.py line 293
[22:45:18] Site:1iD5ZQ..duGz Update for content.json looks valid, saving...
The entire address, 1MusicXkuN2pk5hRdmroeyaCLDJtzTicpB
Does this happen during signing of the site (or user file) or not?
Looks like the content.json contains neither old-style sign nor new-style sign. However, it contains other properties like modified. I'm wondering whether official ZeroNet implementation can even generate such invalid files.
Does this happen during signing of the site (or user file) or not?
I was not signing anything at that moment.
I fixed verification of invalid signs in latest rev: https://github.com/HelloZeroNet/ZeroNet/commit/a49fcb017621e8f0b15e7265621476992bb72916