Hello fellow Genodians,
as already hinted to by Norman in the roadmap discussion, the Genodian's website [1] is now live. It is a federated microblogging platform operated by Genode Labs and running on a Genode system (it uses base-hw and runs within an KVM-based VM). All recipes needed for building the system image are available in the genodians.org repository [2].
[1] http://genodians.org [2] https://github.com/genodelabs/genodians.org
The repository also contains the list of all authors whose content is aggregated and published on the website. For more information, e.g. how to participate, please look into the README file.
Since there is probably one or the other rough edge left and we have not yet decided on a plan to replace the self-signed certificate, the current version should be treated as BETA - stuff is allowed to fall off :-).
Regards Josef
Hi,
congratulations on starting Genodians! I already read the first post ;) The one thing I miss a little bit and I'd really like to see is an RSS feed so I don't miss any new posts.
Regards, Johannes
On Monday, 7 January 2019 16:52:43 CET Josef Söntgen wrote:
Hello fellow Genodians,
as already hinted to by Norman in the roadmap discussion, the Genodian's website [1] is now live. It is a federated microblogging platform operated by Genode Labs and running on a Genode system (it uses base-hw and runs within an KVM-based VM). All recipes needed for building the system image are available in the genodians.org repository [2].
[1] http://genodians.org [2] https://github.com/genodelabs/genodians.org
The repository also contains the list of all authors whose content is aggregated and published on the website. For more information, e.g. how to participate, please look into the README file.
Since there is probably one or the other rough edge left and we have not yet decided on a plan to replace the self-signed certificate, the current version should be treated as BETA - stuff is allowed to fall off :-).
Regards Josef
Hi Johannes,
On 09.01.19 12:04, Johannes Kliemann wrote:
The one thing I miss a little bit and I'd really like to see is an RSS feed so I don't miss any new posts.
good call. I just added an RSS feed in [1] so we can test it tomorrow.
@Josef: Would you like to give it a spin?
[1] https://github.com/genodelabs/genodians.org/commit/42cbf2e86b1594d7ff06b26f8...
Cheers Norman
Very nice. I like it.
Curiosity led me into having a look at the recipes. I am a bit puzzled about the '/dev/random' emulation though as I'd expect that it is accessed by openssl. Is there any reasonable explanation for this or is it one of the reasons why it is treated as BETA?
Cheers Johannes
On Mon, 7 Jan 2019 16:52:43 +0100 Josef Söntgen josef.soentgen@genode-labs.com wrote:
Hello fellow Genodians,
as already hinted to by Norman in the roadmap discussion, the Genodian's website [1] is now live. It is a federated microblogging platform operated by Genode Labs and running on a Genode system (it uses base-hw and runs within an KVM-based VM). All recipes needed for building the system image are available in the genodians.org repository [2].
[1] http://genodians.org [2] https://github.com/genodelabs/genodians.org
The repository also contains the list of all authors whose content is aggregated and published on the website. For more information, e.g. how to participate, please look into the README file.
Since there is probably one or the other rough edge left and we have not yet decided on a plan to replace the self-signed certificate, the current version should be treated as BETA - stuff is allowed to fall off :-).
Regards Josef
Hello Johannes,
Curiosity led me into having a look at the recipes.
It is nice to see that somebody took the time and looked at the scenario more closely.
I am a bit puzzled about the '/dev/random' emulation though as I'd expect that it is accessed by openssl. Is there any reasonable explanation for this or is it one of the reasons why it is treated as BETA?
Well, it would be one of the reasons indeed - using such high-quality entropy was a reasonable choice during the initial development of the scenario. After all, at this point, the features provided by the TLS stack were not that important and now there are still more pressing issues to resolve (functionality-wise). That being said, it will be changed to use a proper entropy source eventually :-)
Regards