You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repository is part of the [eclipse-biscuit](https://projects.eclipse.org/projects/technology.biscuit) project. It is licensed under `BSD-3-Clause` and requires contributors to sign the [Eclipse Contributor Agreement](https://www.eclipse.org/legal/ECA.php) (see #eclipse-contributor-agreement below).
4
+
5
+
## Before contributing
6
+
7
+
This is an implementation of the biscuit specification. All changes pertaining to the specification must be discussed in the [specification repo](https://github.com/eclipse-biscuit/biscuit) first.
8
+
9
+
Unless you’re fixing a trivial issue, it is a good idea to start by opening an issue, in order to gather feedback about the changes you have in mind.
10
+
11
+
You can also ask questions on the [implementers matrix chat](https://matrix.to/#/!suybZZpOqChdTNuIVA:matrix.org).
12
+
13
+
## Code organization
14
+
15
+
-`biscuit` provides core support for biscuit-auth
16
+
-`biscuit-servant` provides support for protecting servant applications
17
+
-`biscuit-wai` provides WAI middlewares for protecting WAI applications
18
+
19
+
## Project communication
20
+
21
+
The discussion space is a [matrix chat](https://matrix.to/#/!MXwhyfCFLLCfHSYJxg:matrix.org).
22
+
Updates are also posted on [bluesky](https://bsky.app/profile/biscuitsec.org) and [mastodon](https://hachyderm.io/@biscuitauth).
23
+
24
+
Security issues can be reported via [github](https://github.com/eclipse-biscuit/biscuit-haskell/security).
25
+
26
+
## Eclipse Contributor Agreement
27
+
28
+
From the [ECA FAQ](https://www.eclipse.org/legal/eca/faq/):
29
+
30
+
The purpose of the ECA is to provide a written record that you have agreed to provide your contributions of code and documentation under the licenses used by the Eclipse project(s) you're contributing to. It also makes it clear that you are promising that what you are contributing to Eclipse is code that you wrote, and you have the necessary rights to contribute it to our projects. And finally, it documents a commitment from you that your open source contributions will be permanently on the public record.
31
+
32
+
In order to sign the ECA, you can follow these steps:
33
+
34
+
-[Create an account](https://dev.eclipse.org/site_login/createaccount.php) on dev.eclipse.org
35
+
- Open your [Account Settings tab](https://dev.eclipse.org/site_login/myaccount.php#open_tab_accountsettings), enter your GitHub ID and click Update Account
36
+
- Read and [sign the ECA](https://dev.eclipse.org/site_login/myaccount.php#open_tab_cla)
37
+
- Use the exact same email address for your Eclipse account and your commit author.
Copy file name to clipboardExpand all lines: README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,15 +8,18 @@ You will find below the main lib and its companions:
8
8
9
9
*[biscuit](./biscuit/) — Main library, providing minting and signature verification of biscuit tokens, as well as a datalog engine allowing to compute the validity of a token in a given context
10
10
*[biscuit-servant](./biscuit-servant) — Servant combinators, for a smooth integration in your API
11
+
*[biscuit-wai](./biscuit-wai) — WAI middlewares for protecting WAI applications with biscuits
11
12
12
13
## Supported biscuit versions
13
14
14
-
The core library supports [`v3` and `v4` biscuits][spec] (both open and sealed).
15
+
The core library supports [`v3.0` to `v3.3` biscuits][spec] (both open and sealed).
16
+
17
+
Only `ed25519` signatures are supported. `p256r1` signatures are not supported yet.
0 commit comments