[tahoe-dev] Dusting off lafs-rpg.

[Callme Whatiwant]

Hi there,

I just realized issues and pull requests related to lafs-rpg have been
filtered away into an old dusty chest locked in my metaphorical attic.
 So, I just made a pass on the open issues, all of which are about 16
months old.

Here are the remaining open issues:

https://bitbucket.org/nejucomo/lafs-rpg/issues?status=new&status=open

If anyone wants to chip in, almost all of those are quick projects.
Some of them, such as CentOS/ubuntu improvements can probably be done
more efficiently by people using those platforms.

I'd also like to fix the install.sh to not silently fail and to
anticipate more platforms.


Also, there's a pull request from Patrick MacDonald for nailing down
TLS cipher suites:

https://bitbucket.org/nejucomo/lafs-rpg/pull-request/1/added-support-for-strong-ssl-ciphers-with/diff

Thanks Patrick!  Before I accepted this, I was hoping people with more
knowledge of recent TLS vulnerabilities and/or forward secrecy could
take a glance at the cipher list and comment on if it's still "Today's
Best TLS config".


I suspect people who use lafs-rpg use it once to generate a config
file, and there-after they simply edit their config and stop relying
on lafs-rpg.  If anyone using a read-only nginx config took some time
to notice if any changes they've made are generally useful, I'd
appreciate pull requests or issues.

Also, I haven't personally been using nginx + lafs for a while,
although I plan on doing so in the future.  If anyone notices changes
in more recent versions of either nginx or tahoe-lafs that warrant
updates, let me know.


Regards,
Nathan / nejucomo