Ejabberd sucks install#
Ejabberd sucks android#
Ejabberd sucks software#
Ejabberd sucks code#

To be ready for the demo, the system must import the keys of pre-authorized users, those users must download and install their PGP-SSL-client-certificate from the server, available over the demo's LAN.

To do this, each service on the box must use the client certificate's user identifier as the user's service id, and must defer to the box's centralized authorization layer to determine whether that user can access that service or not. We could do that through a few services, like Jabber (ejabberd server and jwchat web UI), ownCloud, ikiwiki, or others. If we were to make a presentation where Debian Developers, or anyone in the strongly trusted set of PGP keys, could automatically log into a service as themselves and communicate, that'd be pretty memorable. Users should be able to interact with one another, like in a chatroom. To be interactive, users need to be able to log into the system and use the service. Otherwise, this doesn't affect the standard PGP trust-model at all: in the standard PGP threat-model, anyone can already create a key for anybody, anyway. Since the SSL client certificate is self-validating, the client can verify that the server isn't deceiving it (the client certificate must refer back to the client's original PGP key). To make HTTP client certificates easy, (1) the server must be able to provide clients with SSL Client Certificates based on their PGP keys, and (2) the client must be able to import the SSL Client Certificate from the server. If the server and client can do those things, we've made HTTP client certificates possible, but not easy. log in to the server with a client certificate. To do this, the client needs to be able to:ġ. configure the available services and authorized users in a centralized service configuration system. authorize or deny specific users in an HTTP-session based on a centralized service authorization system, and, 3. identify specific users in an HTTP-session based on PGP keys, 2. To do this, the server needs to be able to:ġ. Right now, in June 2015, the FreedomBox project is pretty close to accomplishing something completely new: making PGP-based client certificate authentication easy. To be memorable, the demo should do something that no demo has done before.

Ejabberd sucks software#

The system will use freely-designed hardware, that which the four fundamental software freedoms can be applied to.

The system will not include any binary blobs in any drivers, and none will be needed to use the fully functional system. fully-free The system will be created from fully-free components, at the software, firmware, and hardware level: software The system will use only the Debian-main archive. interactive The audience can participate with and operate on the running system. The demo needs to showcase an interesting arrangement or combination of technologies that the FreedomBox supports. We would like to have an memorable and interactive demo on a fully-free system ready by October, 2015 or January, 2016.

Client Certificate Keyring Import Extension.

Plinth PGP-Key and PGP-SSL-Client-Certificate Creation.

Apache Client Certificate Identification.

Administrative Service Access Control Layer (ACL).

Client Certificate Identification (Authentication).

It does not look like these projects become worse for the lack of Erlang and it's GC (Elang later returned but this is probably because they wanted to reuse existing Erlang investments rather then some intrinsic Erlang's advantages). Tiny bit-shufflers can be written in any language with or without GC (in fact if you'll read about Erlang's history you'll see that it was open-sourced when Ericsson decided to ban it from all new projects. There are so much hype around Erlang, but I'm yet to see anything complex in it. It's good enough for 99.9999% telephony apps (see: Erlang). precisely where Java with it's GC is involved.

Ejabberd sucks android#

It's only when you need to show UI and react to it (music synthesis, etc) is where Android sucks (when compared to iOS) - i.e. All the audio-related tasks where Java is not involved (i.e.: simple playback or recordng) work fine on Android. Java is also used in all the manipulations of audio.

Ejabberd sucks code#

>but Android's poor audio latency tend to answer no.Īndroid's audio stack is native :) Java code is used only to set up the audio connections. In reply to: Quotes of the week by Cyberax Posted 6:36 UTC (Mon) by khim (subscriber, #9252)