• Joined on 2025-04-19
idk commented on issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:32 -04:00
NetDB: LS not built for subsession

Recent discussion in IRC was that subsessions were broken in -1 (symptom: Unsupported Crypto) and fixed in -5, but that sounds like a client-side problem. This is a server-side issue.

idk commented on issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:31 -04:00
NetDB: LS not built for subsession

Oh so I kind of re-created the subdb-on-the-fly issues but hid them from myself. Typical. Caught up on the discussions with dr

idk commented on issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:31 -04:00
NetDB: LS not built for subsession

np. you were incorrectly creating a subdb for a subsession and whomping/losing the subdb you created for the primary session. That's what I missed in the MR review. So the new one didn't have the…

idk commented on issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:31 -04:00
NetDB: LS not built for subsession

Thank you. I'm sorry for screwing it up, looking forward to your MR for better understanding of what is going wrong. Obviously I am continuously missing it.

idk commented on issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:31 -04:00
NetDB: LS not built for subsession

This is due to bugs in CCR introduced in MR !120 that I partially didn't catch and partially did but didn't fight hard enough for. Reassigning to myself because it's going to be easier than…

idk opened issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:30 -04:00
NetDB: LS not built for subsession
idk closed issue I2P_Developers/i2p.i2p#39 2025-04-21 14:58:30 -04:00
NetDB: LS not built for subsession
idk opened issue I2P_Developers/i2p.i2p#38 2025-04-21 14:58:29 -04:00
Remove FNDS.useSubDBs() option
idk closed issue I2P_Developers/i2p.i2p#38 2025-04-21 14:58:29 -04:00
Remove FNDS.useSubDBs() option
idk commented on issue I2P_Developers/i2p.i2p#36 2025-04-21 14:58:28 -04:00
Unused method FNDF.minFloodfillPeers()

Closed by !141

idk opened issue I2P_Developers/i2p.i2p#37 2025-04-21 14:58:28 -04:00
Unused method LookupDestJob.toBase32()
idk closed issue I2P_Developers/i2p.i2p#37 2025-04-21 14:58:28 -04:00
Unused method LookupDestJob.toBase32()
idk commented on issue I2P_Developers/i2p.i2p#35 2025-04-21 14:58:27 -04:00
Jcpuid-Jbigi error in 2.3.0-8 with RN's build

It is not the hardened security.

Probably not the fault of Canon or Plus, but I can't be 100% sure. Could also have been something random the user did to their files.

The user had some backups…

idk commented on issue I2P_Developers/i2p.i2p#35 2025-04-21 14:58:27 -04:00
Jcpuid-Jbigi error in 2.3.0-8 with RN's build

Thanks for the link. Yes it is a hardened flavor. We are investigating the security restrictions. I'll report back if we find a fix.

idk commented on issue I2P_Developers/i2p.i2p#35 2025-04-21 14:58:27 -04:00
Jcpuid-Jbigi error in 2.3.0-8 with RN's build

So it's complaining about our 64-bit libjcpuid. You can ignore the 2nd failure, of the 32-bit one, which it just tried as a fallback.

Did some research and the key doc on executable stack…

idk opened issue I2P_Developers/i2p.i2p#36 2025-04-21 14:58:27 -04:00
Unused method FNDF.minFloodfillPeers()
idk closed issue I2P_Developers/i2p.i2p#36 2025-04-21 14:58:27 -04:00
Unused method FNDF.minFloodfillPeers()
idk commented on issue I2P_Developers/i2p.i2p#34 2025-04-21 14:58:26 -04:00
Disallow RIs in subdbs

Edited OP, I can tackle most of this

idk opened issue I2P_Developers/i2p.i2p#35 2025-04-21 14:58:26 -04:00
Jcpuid-Jbigi error in 2.3.0-8 with RN's build
idk closed issue I2P_Developers/i2p.i2p#35 2025-04-21 14:58:26 -04:00
Jcpuid-Jbigi error in 2.3.0-8 with RN's build