3 ms·

Thanks for your DPI work. I tested the gemini plugin and works very well. My only complain is that it keeps asking to confirm new keys every time a new server

Thanks for your DPI work. I tested the gemini plugin and works very well. My only complain is that it keeps asking to confirm new keys every time a new server is visited which causes a lot of friction to explore several gemini servers. I understand that is a tradeoff between usability and security, but I wish there was a better solution than that. For now I uploaded Charles plugin written in shell script[1], which always trusts the certificate. [1]: https://github.com/dillo-browser/dillo-plugin-gemini/ https://github.com/dillo-browser/dillo-plugin-gemini/ But I'm considering switching to the Go version if I can find a way to improve the UX. Also, I kindly ask you to add the tag "dillo-plugin" so you can make Dillo plugins easily discoverable by searching for the tag in GitHub[2]. [2]: https://github.com/topics/dillo-plugin https://github.com/topics/dillo-plugin > I believe that in recent versions of Dillo, even https is implemented as a DPI plugin. This was done initially[3] (before 2007) but it was moved to the browser itself[4] in 2016. [3]: https://github.com/dillo-browser/dillo/commits/afd2763caa56dde5c7bd0048a0bc242e3b402fb9/dpi/https.c https://github.com/dillo-browser/dillo/commits/afd2763caa56d... [4]: https://github.com/dillo-browser/dillo/commit/bf5a7783f4a1925c114aad7a89d8f09b600aabe8 https://github.com/dillo-browser/dillo/commit/bf5a7783f4a192...

boomlinde 3y ago
> My only complain is that it keeps asking to confirm new keys every time a new server is visited which causes a lot of friction to explore several gemini servers. Hmm, yeah, it's a trade off. It never annoyed me personally so I haven't given it much thought, but I could add some means to configure this behavior. There should be a commit shortly. I've been meaning to change how it behaves when the certificate differs from the pinned one as well, because as it is now you manually have to remove the old pinned certificate from the file system when a certificate is replaced, which isn't great but at least should happen much less often. > Also, I kindly ask you to add the tag "dillo-plugin" so you can make Dillo plugins easily discoverable by searching for the tag in GitHub[2]. Thanks for the heads up! Done. > This was done initially[3] (before 2007) but it was moved to the browser itself[4] in 2016. I see, so I had the chronology mixed up :).
boomlinde 3y ago
I've updated the plugin so that you can switch between auto pinning and confirmation now, via a configuration file!
- rodarima 3y ago
  Thank you! :-)

boomlinde 3y ago

> My only complain is that it keeps asking to confirm new keys every time a new server is visited which causes a lot of friction to explore several gemini servers. Hmm, yeah, it's a trade off. It never annoyed me personally so I haven't given it much thought, but I could add some means to configure this behavior. There should be a commit shortly. I've been meaning to change how it behaves when the certificate differs from the pinned one as well, because as it is now you manually have to remove the old pinned certificate from the file system when a certificate is replaced, which isn't great but at least should happen much less often. > Also, I kindly ask you to add the tag "dillo-plugin" so you can make Dillo plugins easily discoverable by searching for the tag in GitHub[2]. Thanks for the heads up! Done. > This was done initially[3] (before 2007) but it was moved to the browser itself[4] in 2016. I see, so I had the chronology mixed up :).

boomlinde 3y ago

I've updated the plugin so that you can switch between auto pinning and confirmation now, via a configuration file!

rodarima 3y ago
Thank you! :-)