Here is a list of the projects that I'm interested in working on. If you'd like to help, either w/ time or money, let me know!
Here is a list of the projects that I'm interested in working on. If you'd like to help, either w/ time or money, let me know! Note that some of these projects do have some code behind them.
* File/object metadata.
The ability to tag files w/ data, and share them out. This includes things like tagging people in photos, but also where the file came from. An example of the later is being able to find out what OS release/version of /bin/ls is currently on your system, and where it might be found.
@@ -11,4 +11,7 @@ Here is a list of the projects that I'm interested in working on. If you'd like
An infrastructure to be able to describe conversion from a byte stream to a key/value type structure, and the ability to tie them together. This would generate both a serializer and a deserializer from the same definition.
* [FreeBSD test lab](https://www.funkthat.com/gitea/jmg/fbsdembdev)
A lab where other FreeBSD commiters (at first) can reserve an embedded board, and do testing on it remotely. They will have a jail w/ full access to the network of the board under test, along w/ the ability to power cycle the board. This will hopefully allow more testing of boards.
* Secure/Privacy DNS Resolver. This is an attempt to improve the privacy of DNS resolution. The idea is that for domains that support DNSSEC, do the query over tor, and authenticate the responses, this gives the privacy of tor. If a domain doesn't support DNSSEC, provide various options, either, forward to your ISP's resolver, validate through mulpitle tor queries or other options.
* Secure/Privacy DNS Resolver.
This is an attempt to improve the privacy of DNS resolution. The idea is that for domains that support DNSSEC, do the query over tor, and authenticate the responses, this gives the privacy of tor. If a domain doesn't support DNSSEC, provide various options, either, forward to your ISP's resolver, validate through mulpitle tor queries or other options.
* Next gen secure transport.
A new transport that is designed for privacy and security. Basic idea is that machines establish a tunnel, and any connections between the machines are passed through the tunnel. Similar to QUIC, but drop requirement that it's HTTP traffic. Other advantages is that due to cryptography authentication, multipath and moving IP addresses is an easy thing, as the machine can just create a new tunnel, and tell the old machine to transfer/use this new tunnel as well. Best would be to use a new protocol to be siblings to TCP or UDP, but it's unlikely to work w/ modern nat infrastructure (unless it's IPv6), so UDP will likely be used.
