bitmask_thunderbird.git, branch master [bitmask_thunderbird] Update changelog to 0.0.9 2018-05-08T16:15:28+00:00 Ruben Pollan meskio@sindominio.net 2018-05-08T16:15:28+00:00 3db87dad40a7b73f774ade2810ddd1c048740527

Add support for Thunderbird 60 2018-05-06T22:48:06+00:00 Sukhbir Singh sukhbir@torproject.org 2018-05-06T22:48:06+00:00 91c3b57c9717721914390fa796416584cb5b9c55 See https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 for changes relevant to Thunderbird 60. This commit also bumps up the minimum supported version to Thunderbird 52.
See https://wiki.mozilla.org/Thunderbird/Add-ons_Guide_57 for changes
relevant to Thunderbird 60. This commit also bumps up the minimum
supported version to Thunderbird 52.
Update changelog 2018-04-12T18:47:24+00:00 Ruben Pollan meskio@sindominio.net 2018-04-12T18:47:24+00:00 b154fe2aa6fab711f8e5fe6ff16756b41d2920d7

[feat] Display notification to manually fetch messages if Bitmask is shut down 2018-03-01T22:21:01+00:00 Sukhbir Singh sukhbir@torproject.org 2018-02-27T16:30:54+00:00 0d04d39353556fe6ba7c72592f949c984c67fc94 If Bitmask is shut down and Thunderbird is still running, notify the user using an alert to refresh the session by manually fetching messages ("Get new messages"). Otherwise if Bitmask has shut down and Thunderbird tries to fetch messages, it will throw up an error and to refresh the session, the user has to manually fetch the messages. There can be better ways of handling this but for now we should just make sure that the user knows why the messages are not being fetched in case Bitmask stops running or is shut down. Another solution can be to check for messages automatically for the user after Bitmask is running to refresh the session but the reason this approach was not preferred was because the user may not wish to check for new messages and force-checking would not be transparent. (Not to forget, the XUL hacks :) This commit also removes a redundant string bundle call.
If Bitmask is shut down and Thunderbird is still running, notify the
user using an alert to refresh the session by manually fetching messages
("Get new messages"). Otherwise if Bitmask has shut down and Thunderbird
tries to fetch messages, it will throw up an error and to refresh the
session, the user has to manually fetch the messages.  There can be
better ways of handling this but for now we should just make sure that
the user knows why the messages are not being fetched in case Bitmask
stops running or is shut down.

Another solution can be to check for messages automatically for the user
after Bitmask is running to refresh the session but the reason this
approach was not preferred was because the user may not wish to check
for new messages and force-checking would not be transparent. (Not to
forget, the XUL hacks :)

This commit also removes a redundant string bundle call.
[feat] Display encryption status when viewing a message 2018-01-29T21:50:52+00:00 Sukhbir Singh sukhbir@torproject.org 2018-01-13T05:44:14+00:00 89d99387f7b72b5f629266c61c733974014cfdea Display a notification bar in the message pane if the message was encrypted for messages in the "Inbox" folder. For messages in the "Sent" folder, we have placeholder code for displaying the message state and for adding custom headers if required. However, we need to understand how to handle the case for multiple recipients with different encryption states since it's possible to send encrypted messages to recipients with known keys but the same message will be send unencrypted to recipients whose keys are not known. In such a case we can display the message status per-recipient.
Display a notification bar in the message pane if the message was
encrypted for messages in the "Inbox" folder.

For messages in the "Sent" folder, we have placeholder code for
displaying the message state and for adding custom headers if required.
However, we need to understand how to handle the case for multiple
recipients with different encryption states since it's possible to send
encrypted messages to recipients with known keys but the same message
will be send unencrypted to recipients whose keys are not known. In such
a case we can display the message status per-recipient.
[feat] Display encryption status of email addresses in compose window 2017-12-27T03:06:42+00:00 Sukhbir Singh sukhbir@torproject.org 2017-12-26T17:11:53+00:00 3084a2f99dafa173f3d0ee4128e0a43d6ba62b3c When composing an email, display the encryption status for each address. If the public key for a given address is found, show the "lock" sign (encrypted) in front of it otherwise show the "unlocked" sign (unencrypted). This status is fetched using the keymanager.
When composing an email, display the encryption status for each address.
If the public key for a given address is found, show the "lock" sign
(encrypted) in front of it otherwise show the "unlocked" sign
(unencrypted). This status is fetched using the keymanager.
[feat] Add icons to bitmask status bar 2017-12-20T16:09:55+00:00 Sukhbir Singh sukhbir@torproject.org 2017-12-17T17:05:35+00:00 72468d21084a80420b299d94a6afdd66c2d141e6 Display the status of bitmaskd in Thunderbird's status bar by connecting to it using bitmask.js
Display the status of bitmaskd in Thunderbird's status bar by connecting
to it using bitmask.js
[feat] Display status of bitmaskd in status bar 2017-12-18T09:18:12+00:00 Sukhbir Singh sukhbir@torproject.org 2017-12-17T17:05:35+00:00 de0dc0bb86f79234159d32684003bb205240e07c Display the status of bitmaskd in Thunderbird's status bar by connecting to it using bitmask.js
Display the status of bitmaskd in Thunderbird's status bar by connecting
to it using bitmask.js
formatting for the readme 2017-10-30T17:15:21+00:00 Kali Kaneko kali@leap.se 2017-10-30T17:15:21+00:00 3539bf51777b4c979546758066bdc76cfa0872da

[doc] add release instructions to README 2017-10-30T16:33:44+00:00 drebs drebs@riseup.net 2017-10-30T16:33:44+00:00 e21933fd124b709a419096fa8a6dd16a449018d2