mirror/libsignal
0
0
Fork 0
mirror of https://github.com/signalapp/libsignal.git synced 2024-09-20 03:52:17 +02:00
Code
f6e5f9772f
libsignal/.gitignore

30 lines
392 B
Plaintext
Raw Normal View History

Create initial commit of signal protocol rust This supports XEd25519 and has some protobuf compilation going on but not much else yet at this point.
2020-04-21 06:24:31 +02:00
/.idea
Increase local JNI frame to 8192 for all JNI calls This is overkill for most calls but multi-recipient messages require potentially a lot of objects. The codegen is in the way of making a surgical change at the moment so hitting it with a broad fix for now. May return to add a conditional to the macro definition later.
2021-09-09 18:56:29 +02:00
*.iml
Create initial commit of signal protocol rust This supports XEd25519 and has some protobuf compilation going on but not much else yet at this point.
2020-04-21 06:24:31 +02:00
/target
gitignore Swift's build directory too
2020-10-16 22:00:26 +02:00
/swift/.build
Add a Yarn-based Node package for signal-client There's very little here yet, just enough to test something.
2020-10-23 20:44:41 +02:00
/node/dist
Move package.json inside the node/ directory Previously all APIs were available through the top-level index.ts, but now the zkgroup APIs are in their own module. To access that in the old packaging required writing import * from '@signalapp/signal-client/node/dist/zkgroup' This commit moves the package root into the node/ directory to eliminate the 'node/' component, then adds a top-level, precompiled zkgroup.js/.d.ts so that clients can use import * from '@signalapp/signal-client/zkgroup'
2021-11-09 00:38:12 +01:00
/node/node_modules
/node/build
Ignore editor backups
2020-07-30 19:24:42 +02:00
Node: allow Rust `async` blocks to wait on JavaScript futures Neon provides a way to expose *synchronous* JavaScript functions from Rust. This means that if Rust wants to wait for the result of a JavaScript promise, it can at best return a callback to continue its work when the promise resolves. This does not naturally compose with Rust's `async`, which works in terms of Futures. This commit adds a new crate, signal-neon-futures, that provides functionality for (1) wrapping JavaScript futures so they can be awaited on in Rust, and (2) producing a JavaScript promise that wraps a Rust future. It does so by synchronously resuming execution of the Rust future whenever an awaited JavaScript promise is resolved.
2020-12-04 21:11:51 +01:00
/rust/bridge/node/futures/tests/node-tests/node_modules
Ignore .orig and .rej files from patch
2020-11-04 22:48:50 +01:00
*.orig
*.rej
Ignore editor backups
2020-07-30 19:24:42 +02:00
*~
\#*\#
.\#*
Modify libsignal-protocol-java to use Rust via JNI Removes device consistency code (unused) Removes decryption callbacks (unused)
2020-11-03 22:29:24 +01:00
java/build
java/android/build/
gitignore: Fix new Java build directory paths
2022-03-11 20:27:09 +01:00
java/client/build
java/server/build
Modify libsignal-protocol-java to use Rust via JNI Removes device consistency code (unused) Removes decryption callbacks (unused)
2020-11-03 22:29:24 +01:00
java/.gradle
java/local.properties
java/android/src/main/jniLibs
Java: Add a ProGuard file to preserve our JNI bindings
2022-03-24 23:06:57 +01:00
java/shared/resources/*.dylib
java/shared/resources/*.so
java/shared/resources/*.dll
Add support for M1 and Catalyst architectures via cocoapods
2021-06-09 21:19:49 +02:00
.DS_Store
Copy Permalink