846fb09433
* feature/api-0.3: (37 commits) Rerun on changed BFFHD_BUILD_TAGGED_RELEASE env var Log version on start Make build step only use git info when not building a tagged release Reverse visibility check to properly disclose machines Only return `use` interface if machine is currently free or reserved by me allow bffh to build outside of a git repo enable mutistage auth Fix auth Update API update desfire crate to version on crates.io working Desfire auth in the api! fix stupid logic error initial integration of the X-FABFIRE mechnism Improve TLS support Fixes warnings Port to rsasl2 More cleanup. Makes rumqttc futures run on the tokio runtime as required. Use our own MQTT URL dissector so existing configs don't break Fixing more warnings ...
FabAccess Diflouroborane
Diflouroborane (shorter: BFFH, the chemical formula for Diflouroborane) is the server part of FabAccess. It provides a server-side implementation of the FabAccess API.
What is this?
FabAccess is a prototype-grade software suite for managing access, mostly aimed at Makerspaces, FabLabs, and other open workshops. It is designed to allow secure access control to machines and other equipment that is dangerous or expensive to use. It tries to also be cheap enough to be used for all other things one would like to give exclusive access to even when they are not dangerous or expensive to use (think 3D printers, smart lightbulbs, meeting rooms).
FabAccess uses a Client/Server architecture with a Cap'n Proto API. You can find the API schema files over in their own repository. The reference client is Borepin, written in C#/Xamarin to be able to be ported to as many platforms as possible.
Installation
See INSTALL.md
Contributing
See CONTRIBUTING.md. Thanks!