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
Copy file name to clipboardExpand all lines: README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,23 +13,24 @@ It is in it's current form a subset of the specification.
13
13
There is an alternative implementation under [goto-opensource/secure-frame-ts](https://github.com/goto-opensource/secure-frame-ts)
14
14
15
15
## Differences from the sframe draft
16
-
* Aes-CTR is not implemented
17
16
* ratcheting is not implemented
18
17
* keyIds are used as senderIds
18
+
* no metadata authentication
19
19
20
20
## Supported crypto libraries
21
21
Currently two crypto libraries are supported:
22
22
-[ring](https://crates.io/crates/ring)
23
23
- is enabled per default with the feature `ring`
24
24
- supports compilation to Wasm32
25
+
- Aes-CTR mode ciphers are not supported
25
26
-[openssl](https://crates.io/crates/openssl)
26
27
- is enabled with the feature `openssl`
27
28
- To build e.g. use `cargo build --features openssl --no-default-features`
28
29
- uses rust bindings to OpenSSL.
29
30
- Per default the OpenSSL library is locally compiled and then statically linked. The build process requires a C compiler, `perl` (and `perl-core`), and `make`. For further options see the [openssl crate documentation](https://docs.rs/openssl/0.10.55/openssl/).
30
31
- Compilation to Wasm32 is [not yet supported](https://github.com/sfackler/rust-openssl/issues/1016)
31
32
32
-
Both cannot be enabled at the same time, thus on conflict `sframe`fallsback to using `ring`.
33
+
Both cannot be enabled at the same time, thus on conflict `sframe`issues a compiler error.
33
34
## License
34
35
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
0 commit comments