This project has ended, but ChatSecure iOS continues. For Android, please use Conversations or Zom instead

Moves ImpsProvider (database adapter) to remote process, so that UI process can be reaped by the OS.

ImpsProvider no longer connects directly to CacheWord (that part of the integration didn't seem to do anything).

I' testing Gibberbot on my Android and Pidgin on my Desktop. Both Clients create there own Key. But what happend when i otr-chat with a Friend, one day from gibberbot and the other day from pidgin. Does he gets errors? or always have to readd my keys? How should that work?

I though i need an import function on gibberbot to import my otr-key or a export at gibberbot and an import on the other client.

ChatSecure connects when I start the app, but disconnects some time later without reconnecting. This problem is new since the update from 14.0.2 to 14.0.3. It seems to occur more frequently when other apps are working in the foreground. Signing out and signing in again works, but I would be disconnected after a while again.

Could it be that the login thread, introduced in commit a371353, becomes a victim of the garbage collector after a while in the background? (Didn't find anything suspicious elsewhere in the patches.)

Was previously running Orbot/Tor and Gibberbot without issue (Motorola Razor Maxx and a Samsung Galaxy S3).

Now with the recent update switching from Gibberbot to Chatsecure we can text between both devices securely but we cannot send files or pictures to one another.

Did I read this another post correctly in that this is NOT possible?

I have built asmack-jse.jar from latest guardianproject asmack master branch (06a2c8363e), but the jar does not work with current Gibberbot. Here is the compile error:

The method setCustomSSLContext(SSLContext) is undefined for the type ConnectionConfiguration    XmppConnection.java /Gibberbot/src/info/guardianproject/otr/app/im/plugin/xmpp  line 680    Java Problem

it seems that the function "ConnectionConfiguration.setCustomSSLContext" is missing.

For me and my friends it's really annoying that 14.2.0 is re- and resending the last message to the receiver even if it already arrived. AFAIS happens this always after reconnecting. So if if you have an unstable connection this is really a no go and we had to downgrade to 14.1.1-rc5 until this problem is solved.

But thank you for the good work on ChatSecure keep going on. :-)

• Remove CacheWord handling from AccountListActivity. CacheWord handling is now centralized in WelcomeActivity
• Remove CacheWord handling from ImApp
• ImpsProvider is now responsible for initializing OtrKeyStore password
• WelcomeActivity goes to AccountListActivity if it can open the DB without user intervention

I use Gibberbot to chat using Google-talk account. Other side is mostly Pidgin on Debian GNU/Linux. Sometimes messages that are sent from Pidgin to Gibberbot are simply lost. There is no error message or something on any side of communication. That is really bad since most of the time I do not notice that message is lost. I never have such a problem with Pidgin<->Pidgin. I believe this is very serious bug.

Please ask questions if you need more info. I will temporary switch to Xabber now.

Hi, Just tried the latest nightly build from here https://guardianproject.info/builds/ChatSecure/ on an S3 (jellybean) and a Nexus 7 (kitkat).

Previously I had had a good experience with 13.0.3, but the latest nightly seems to have gotten buggier (at least for me).

Here's the problem. User 1 invites user 2, but they still appear offline to each other, and encryption never starts (keeps spinning forever but no crypto happens).

I run my own basic prosody server, and I can see in the mysql database that they are indeed subscribed to each other (both), so the add contact function seems to have worked. Here's what I see in the roster in the DB: {"subscription":"both","name":"1","groups":{"Buddies":true}} {"name":"2","groups":{"Buddies":true},"subscription":"both"}

I also see the following entry for both users, which maybe the source of the problem: I have as value {}, with the indication "pending" in user 1 and user 2's roster.

Should chatsecure be creating the empty pending or is this a bug?

Thanks, Peter

this began as actionbar menu tuning, and expanded to some more general UI improvements from initial user feedback

• removed colorful background images (will allow user to define/set)
• added back in list / no avatar mode for contacts with grid/list switch pref
• removed menu below chat, and moved all functions to actionbar (in progress, nearly done)

a little more to do, then want to test, and push to Beta group

Thanks for gibberbot.

An issue with the latest 9/16 build:

1. start gibberbot for the first time
2. fill in username and password, leaving advanced settings untouched
3. click "sign in"
4. I get a generic connection error. the logs say "Server does not support compatible authentication mechanism." I get this error whenever "allow plain text auth" is enabled. This seems like a bug in its own right, because enabling plain text auth should not force plain text auth, but regardless, the point here is that "allow plain text auth" was NOT checked when i hit sign in, but now it is attempting plain text auth.
5. hit back button and edit advanced settings.
6. "allow plain text auth" has now been mysteriously checked. uncheck it.
7. click "sign in"
8. success

My conclusion: when setting up a new account, the visible defaults are ignore and "allow plain text auth" is enabled. For a chat app with a focus on security, I think this is not advisable (!).

The other advanced setting that is mysteriously altered is the "connect server" option. it goes from blank to the domain of the JID. In my case, I can still connect even though the incorrect "connect server" value is set, because the SRV record is still used, but ideally "connect server" would stay blank (and also override the SRV record if present).

Keep up the good work.

I use chatsecure with last version of server openfire in first login no problem but later "after save the certificate " not login and show the exception : W/System.err: javax.net.ssl.SSLProtocolException: Read error: ssl=0xaf749200: Failure in SSL library, usually a protocol error W/System.err: at com.android.org.conscrypt.NativeCrypto.SSL_read(Native Method)

Android : 5.01 any help ?

Please update chat secure 14.3 clean version on f droid and your repository 14.3 version only aviable for google play i dont trust play market or 14.3 its unofficial version ?

Dear developers,

In the position: https://github.com/guardianproject/ChatSecureAndroid/blob/master/src/info/guardianproject/otr/app/im/plugin/xmpp/XmppConnection.java#L389 The bitmap object of "b" can be recycled timely because the app will never use it after writing a compressed version of it to the specified output stream.

I found that you have done the same thing in the following code area： https://github.com/guardianproject/ChatSecureAndroid/blob/master/src/info/guardianproject/otr/app/im/app/ChatFileStore.java#L290

I received the following email from Google when I tried to add my Google account in ChatSecure (the account addition in the app was stuck on 'logging in')

Review blocked sign-in attempt

Hi , Google just blocked someone from signing into your Google Account from an app that may put your account at risk. Less secure app * Don't recognize this activity? If you didn't recently receive an error while trying to access a Google service, like Gmail, from a non-Google application, someone may have your password.

[SECURE YOUR ACCOUNT]

Are you the one who tried signing in? Google will continue to block sign-in attempts from the app you're using because it has known security problems or is out of date. You can continue to use this app by [allowing access to less secure apps], but this may leave your account vulnerable.

Best, The Google Accounts team *The location is approximate and determined by the IP address it was coming from. This email can't receive replies. For more information, visit the Google Accounts Help Center.

I'm not sure why they call it a "less secure app.", or whether anything can be done to mitigate this. Just putting it here for the sake of information.

Thank you for ChatSecure!

PS: perhaps https://guardianproject.info/howto/chatsecurely/ should be updated to reflect this, among other things?