88475bdd54
Transport properties client. #229
2016-01-27 12:51:55 +00:00
e370cafb12
Moved classes from messaging package to sync package.
2015-12-15 15:05:06 +00:00
9868feeb2a
Refactor KeyManager and TagRecogniser. #55
2015-12-14 11:02:49 +00:00
123dff3a3d
Don't mix JUnit 4 annotations with JUnit3 TestCase.
2015-12-08 14:53:50 +00:00
7841ae52ca
Renamed SerialModule, fixed Roboguice module list.
2015-11-30 16:47:33 +00:00
027ae8340f
Whitespace-only code formatting changes.
2015-11-30 09:38:25 +00:00
41c4c4d808
Renamed raw data type.
2015-05-02 21:05:23 +01:00
b8e37a5421
Renamed serial component to data, moved consumers to briar-core.
2015-05-02 20:39:24 +01:00
416719e3d9
Removed silly SerialComponent interface.
2015-05-02 20:30:25 +01:00
32c9ce50d9
Moved the messaging protocol one step closer to BSP.
...
This breaks backward compatibility for the wire protocol and messages
stored in the database. The database schema version has been
incremented.
2015-05-01 16:59:27 +01:00
112d80420c
Downgrade to 256-bit curve for performance.
...
Also reduced hash function to 256 bits because our target security level
is now 128 bits.
2015-01-09 13:23:44 +00:00
d3bf2d59a1
Use the same maximum frame length for all transports.
2015-01-05 16:24:44 +00:00
358166bc12
Don't try to erase secrets from memory.
...
1. The things we're really trying to protect - contact identities,
message contents, etc - can't be erased from memory because they're
encapsulated inside objects we don't control.
2. Long-term secrets can't be protected by erasing them from memory
because they're stored in the database and the database key has to be
held in memory whenever the app's running.
3. If the runtime uses a compacting garbage collector then we have no
way to ensure an object is erased from memory.
4. Trying to erase secrets from memory makes the code more complex.
Conclusion: Let's not try to protect secrets from an attacker who can
read arbitrary memory locations.
2014-12-29 21:08:27 +00:00
f316d64afa
Moved stream crypto to crypto component.
2014-12-29 19:55:05 +00:00
388b36b6be
Check periodically for retransmittable packets. Bug #46 .
2014-12-14 20:26:41 +00:00
1d20761123
Messaging sessions aren't responsible for closing their streams.
...
The TransportReader/Writer's dispose() method should handle that, and
ConnectionManager is responsible for calling it.
2014-11-06 13:13:23 +00:00
852a618cb3
Interrupt messaging session if contact or transport is removed.
2014-11-06 08:10:29 +00:00
4ca83842d1
Moved ConnectionDispatcher and ConnectionRegistry to plugins package.
2014-11-05 19:40:07 +00:00
26d93b83b4
Factored out StreamReader/Writer from messaging layer.
2014-11-05 19:22:01 +00:00
33c3eb7308
PacketWriters aren't responsible for flushing their output streams.
2014-11-04 17:03:06 +00:00
7b8181e309
Massive refactoring to merge handling of simplex and duplex connections.
2014-11-04 16:51:25 +00:00
b24f153704
Renamed a load of things from 'connection' to 'stream'.
2014-10-08 16:21:55 +01:00
8b8df435a5
Separated event infrastructure from DB.
2014-10-03 09:44:54 +01:00
458c0ca285
Don't broadcast MessageAddedEvent if message wasn't added.
...
Fixed a bug in SimplexMessagingIntegrationTest that should've caught
this.
2014-07-04 15:16:56 +01:00
8c18773141
Write the tag immediately even if there are no packets to send. Bug #27 .
2014-03-16 18:13:31 +00:00
71a31c2a7a
Include creation time in LocalAuthor.
...
This allows the oldest LocalAuthor to be used as the default.
2014-02-10 12:14:09 +00:00
822392f9e7
Use strings rather than hashes to identify transports. Dev task #64 .
2014-01-24 10:39:34 +00:00
6af3c54c28
Removed shouldFlush() from plugins, added missing PacketWriter method.
2014-01-15 17:10:25 +00:00
8886d954d7
Reorganised Guice modules. Contribute entropy to pool on Linux/Android.
2014-01-14 19:33:17 +00:00
832476412c
Changed the root package from net.sf.briar to org.briarproject.
2014-01-08 16:18:30 +00:00
akwizgran