a5fd7ff9dc
Added dependency injections for FileUtils and removed redundant code
2015-12-10 11:07:10 +01:00
fb2a44c478
code re-structure, mostly nitpicks :)
2015-12-10 11:02:15 +01:00
886cad91f0
Added a dialog and refactored code
2015-12-10 11:02:15 +01:00
ca00b414e7
Fixed lost code from merge
2015-12-10 11:01:00 +01:00
27edc2e3e8
code and ui refactoring in the Password activity, encapsulation and wrappers.
2015-12-10 11:01:00 +01:00
a5afa2ef93
Merge branch '161-hidden-service-directory' into 'master'
...
Create hidden service in a subdirectory. #161
The permissions for the parent directory are too permissive (775) for Tor 0.2.7.5. Store the hidden service hostname and private key in a subdirectory with permissions 700.
See merge request !5
2015-12-09 13:21:54 +00:00
f4538df679
Touching startup failure notification now shows details
...
The text of the startup failure notification is unhelpful due to lack of
space. Touching the notification now launches an activity that gives details
of the problem and what can be done about it.
Closes #38
2015-12-08 11:52:20 -02:00
f0558ceb7a
Merge branch '159-improve-setup-errors' into 'master'
...
Show setup page error messages by the relevant text box
Closes #159
See merge request !3
2015-12-08 12:59:30 +00:00
2b71e70144
Merge branch '100-hide-strength-meter' into 'master'
...
Hide password strength meter when confirming password
Closes #100
I opted to hide the strength meter because:
* more extensive changes would have been required to set the strength meter to 100% red.
* IMHO it would lead to confusion as to the meaning of the strength meter.
* the "passwords do not match" error should eventually become a proper error of the confirm EditText, not a separate label.
See merge request !2
2015-12-08 12:57:43 +00:00
e4ac6d3afd
Create hidden service in a subdirectory. #161
...
The permissions for the parent directory are too permissive (775) for Tor 0.2.7.5. The subdirectory is created with permissions 700.
2015-12-08 12:26:00 +00:00
383cb651bc
Show setup page error messages by the relevant text box
2015-12-08 07:13:14 +00:00
11deb5728f
Hide password strength meter when confirming password
2015-12-08 06:49:55 +00:00
ceef31599b
Clear the password field if wrong password is entered
2015-12-08 06:06:16 +00:00
53f6f24d53
Don't enable Bluetooth by default. #99
2015-12-03 17:13:49 +00:00
8529c976c2
Renamed a bunch of lock variables.
...
"synchLock" will become confusing when we have lots of objects with "sync" in the name.
2015-12-03 16:39:53 +00:00
427efdc7d6
Raise minimum Java version to 6, upgrade H2. #24
2015-12-02 14:59:51 +00:00
c65ea9a896
Source should be Java 6, don't use diamond operator.
2015-12-02 13:22:23 +00:00
79d9b4b6af
Raised minimum Android version to 2.3 (API 9). #23
2015-12-02 13:20:55 +00:00
db6d277887
Bumped expiry date to 1 Jan 2016.
2015-11-30 11:02:33 +00:00
027ae8340f
Whitespace-only code formatting changes.
2015-11-30 09:38:25 +00:00
dea5a44724
Simpler forum sharing UX.
2015-04-29 15:08:58 +01:00
ec7eb386f5
Bumped expiry date to 15 May 2015.
2015-04-27 15:20:53 +01:00
6135bea2b4
Support Tor on Android x86 (thanks to n8fr8).
2015-04-16 08:02:57 +01:00
92d26f7867
Use strict mode to log potential problems with testing builds.
2015-04-08 08:50:40 +01:00
6e7578a0e0
Don't try to access Build.CPU_ABI2 on API version 7.
2015-04-07 19:11:59 +01:00
f2d3e4cb81
Remove crash handler when handling first crash. Fixes bug #76 .
2015-04-07 19:07:57 +01:00
84596baddb
Bumped expiry date to 1 May 2015.
2015-04-05 16:37:46 +01:00
a1d2aaf10e
Use JDK 1.7, target Android 5.1.
2015-04-03 20:56:01 +01:00
10924709d0
Use PIE Tor binary on API version 16+.
2015-03-23 11:03:00 +00:00
b791ce02b6
Insert padding between password strength meter and progress spinner.
2015-03-23 11:00:54 +00:00
a5b1d92eae
Log discovered devices to track down discovery bugs.
2015-03-11 10:24:53 +00:00
35212a49dc
Bumped expiry date to 1 PAril 2015.
2015-03-05 14:05:24 +01:00
316e4c88fd
Bumped expiry date to 1 March 2015.
2015-02-05 14:32:43 +00:00
c14697972a
Upgraded Tor to 0.2.5.10 with OpenSSL 1.0.2.
2015-01-30 19:23:36 +00:00
f8a4a4920d
Merge branch 'AbrahamKiggundu/briar-master': better lock encapsulation
2015-01-29 11:28:48 +00:00
0dbfd7073f
Comments to indicate which locks guard which variables.
2015-01-29 11:12:41 +00:00
47bd84122e
Code formatting and small cleanups.
2015-01-28 21:18:31 +00:00
7fbad8dc26
Use FortunaGenerator to implement PseudoRandom.
2015-01-14 20:46:03 +00:00
73d4f39726
Bumped expiry date to 1 February 2015.
2015-01-14 16:04:01 +00:00
fcb983a651
Bug#49
...
https://sourceforge.net/p/briar/bugs/49/
Fixed by ensuring that the generated contact and group intents are uniquely identified
2015-01-08 11:58:44 +03:00
851151041e
Pull-Merge of latest changes from main repo
2015-01-08 11:54:47 +03:00
686d5fd206
bug#49 Fixed by ensuring that intents for different contacts/groups can be distinguished from each other when resolving PendingIntent refs
2015-01-08 00:37:10 +03:00
2b9c469063
Merge branch 'improve-thread-encapsulation' into upstream
2015-01-06 07:15:11 +03: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
9a2e93ebb9
cleanup
2014-12-26 17:35:37 +03:00
b074978472
Improved encapsulation of thread synchronisation as follows
...
- replaced use of Object instance mutex with a private final Lock object
- replaced Object signaling with specific condition signalling
2014-12-26 16:40:46 +03:00
388b36b6be
Check periodically for retransmittable packets. Bug #46 .
2014-12-14 20:26:41 +00:00
29a6596ee3
Use the transport's idle timeout, not a hardcoded value.
2014-12-14 15:18:39 +00:00
d4fa656dbb
Application layer keepalives to detect dead TCP connections.
...
DuplexOutgoingSession flushes its output stream if it's idle for a
transport-defined interval, causing an empty frame to be sent. The TCP
and Tor plugins use a socket timeout equal to twice the idle interval to
detect dead connections.
See bugs #27 , #46 and #60 .
2014-12-13 12:00:40 +00:00
Ernir Erlingsson
akwizgran
Torsten Grote
akwizgran
str4d
Alexander Løvik Stevenson
Abraham Kiggundu