Battle plan for migrating to .Net8

[ts678]

@tsuckow

BSD support is probably impractical

FreeBSD just got .NET 8 in their ports system and is working on it. Maybe this will help at some point.

@tsuckow

Encryption of the database is legally encumbered

How so? The SQLite Encryption Extension (SEE) is not used AFAIK, but we do face issue of the weak RC4 encryption being removed from the public domain System.Data.SQLite. One proposed solution is

@kenkendk

Since most Linux distros ship SQLite without the weak RC4 cipher, there is no protection on Linux by default. I think it would be a better solution to simply encrypt the fields in the database (done by the application) instead of using poor encryption on the whole file.

other links at

Which tool can open encrypted DB

Some other discussion about it: Password-protected databases no longer work with 1.113, no rollback possible SQLITE_HAS_CODE is gone? Done as part of some Aug 2019 work. Dodged this encryption issue by chance… Next time will not be that lucky. If I understand you, Windows Duplicati will break. Would you like to open a GitHub Issue so that it can be tracked by development? You look like you probably know C#. Would you be able to help with the solution? Duplicati exists and improves thanks…

but I’m not sure either of these issues has to be solved for some initial builds to move the port forwards.