|
|
@@ -15,3 +15,7 @@ Here is a list of the projects that I'm interested in working on. If you'd like |
|
|
|
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. |
|
|
|
* New file interface architecture. |
|
|
|
The POSIX file interface has served us well, but one thing it lacks is integrity. Anyone that does file writing has to add their own logging/journaling logic, or do the poor man's new file/rename in order to do atomic updates. Modern file systems like ZFS and even UFS w/ softupdates, do this for themselves, but currently there is no exposed interface to allow user land programs to make use of these features. |
|
|
|
* New ZFS interface layer. |
|
|
|
ZFS has a ZPL that mappes the POSIX layer onto ZFS. It'd be nice if there was an interface that exposed the raw ZFS objects to a userland system. This would allow things like a userland program handling it's own lookup layer, and cheaper CAS backed storage. |