[whispersystems] What is TextSecure without Encrypted SMS ?

[Florent B]

Hi everyone,

I'm not a developer, just an user.

What I liked in TextSecure was... encryption.

With last release, no more Encrypted SMS.

What is TextSecure for, now ?

So, I WAS a TextSecure user. bye

Florent

[Jonas]

Hi Florent,

Post by Florent B
I'm not a developer, just an user.
What I liked in TextSecure was... encryption.
With last release, no more Encrypted SMS.

Some people started the new project SMSSecure as a fork of textsecure.
This project aims to provide the encrypted SMS feature that just has
been ripped out of TextSecure. According to the developers, soon the
first release will arrive at F-Droid and on Google Play. Until then, you
can follow the development on Github: https://github.com/SMSSecure/SMSSecure

Cheers,
jonas

Post by Florent B
What is TextSecure for, now ?
So, I WAS a TextSecure user. bye
Florent

[Tim Harman]

Post by Florent B
Hi everyone,

Hi!

Post by Florent B
I'm not a developer, just an user.

Me too.

Post by Florent B
What I liked in TextSecure was... encryption.

Great, well it's still there and working fine.

Post by Florent B
With last release, no more Encrypted SMS.

That's right. Too many support queries from users who had issues with it,
it only works Android<->Android. It's continued inclusion is holding the
project's goals back.

Post by Florent B
What is TextSecure for, now ?

TextSecure is still a way to send encrypted messages to other users using
TextSecure. (The same as it always ways)

TextSecure can now send messages to iOS devices running Signal (This
wasn't possible if you send an encrypted SMS, iPhone's don't allow another
app to read SMS messages)

TextSecure is still a way to ensure that only you can read the SMS
messages on your Android device (The same as it always was)

TextSecure is still open source, auditable and trustable (The same as it
always was)

TextSecure is no longer able to send the encrypted messages via the
SMS/MMS channel, only via the data channel. If that's something you must
have, then yes, TextSecure is sadly no longer for you.

Post by Florent B
So, I WAS a TextSecure user. bye

Goodbye :(

Post by Florent B
Florent

Tim

[Angel Stoleski]

https://github.com/krt16s/SMSSecure/

Post by Tim Harman

Post by Florent B
Hi everyone,

Hi!

Post by Florent B
I'm not a developer, just an user.

Me too.

Post by Florent B
What I liked in TextSecure was... encryption.

Great, well it's still there and working fine.

Post by Florent B
With last release, no more Encrypted SMS.

That's right. Too many support queries from users who had issues with it,
it only works Android<->Android. It's continued inclusion is holding the
project's goals back.

Post by Florent B
What is TextSecure for, now ?

TextSecure is still a way to send encrypted messages to other users using
TextSecure. (The same as it always ways)
TextSecure can now send messages to iOS devices running Signal (This
wasn't possible if you send an encrypted SMS, iPhone's don't allow another
app to read SMS messages)
TextSecure is still a way to ensure that only you can read the SMS
messages on your Android device (The same as it always was)
TextSecure is still open source, auditable and trustable (The same as it
always was)
TextSecure is no longer able to send the encrypted messages via the
SMS/MMS channel, only via the data channel. If that's something you must
have, then yes, TextSecure is sadly no longer for you.

Post by Florent B
So, I WAS a TextSecure user. bye

Goodbye :(

Post by Florent B
Florent

Tim

[Leandro Salvador]

Hi Angel! Cool! =)

A GitHub's newbie question: when you fork a project, is it possible to
track/audit the changes considering the fork moment as the start point of
the new project? Securecom Text apparently erased their history and isn't
possible to audit the changes between the two projects (TextSecure and
SecurecomText) I will paste below part of a topic from the list treating
exactly about this subject:


---------- Forwarded message ----------
From: Sam Lanning <***@samlanning.com>
Date: 2015-03-17 14:59 GMT-03:00
Subject: Re: [whispersystems] A brief suggestion about a future abandoning
of Encrypted SMS TextSecure feature
To:
Cc: ***@lists.riseup.net


They did make the decision to wipe the commit graph and start a fresh
history though... which I consider questionable! It certainly makes it
harder to immediately see what the differences are between the fork and the
original.

Sam.

Every one of their github repos clearly state they're forks from
WhisperSystems.
Thanks Scott! The app seems be great, but I'm not sure it's trustable. I
have doubts because they have three apps, a TextSecure-SMS, a
TextSecure-DATA, and a RedPhone-VOICE clones/forks. It's great, but... they
don't tell it's WhisperSystems forks! The user that discover these apps via
Play Store (and don't know the original) will never know this. I have some
doubts about the intentions of a group that don't share it's a fork and,
consequently, am not sure to trust they software. Do you trust or know the
group?
SMS: https://play.google.com/store/apps/details?id=com.securecomcode.text
https://play.google.com/store/apps/details?id=com.securecomcode.messaging
https://play.google.com/store/apps/details?id=com.securecomcode.voice
(Enviado via Linux Android.)

TL;DR
Thanks for the hard work! I trust you and the other developers so I
ask: do you know of another solution for trustworthy encrypted
messaging over SMS?

https://play.google.com/store/apps/details?id=com.securecomcode.text
https://github.com/Securecom/Securecom-Text

.....
Leandro Salvador

https://github.com/krt16s/SMSSecure/

Post by Florent B
Hi everyone,

Hi!

Post by Florent B
I'm not a developer, just an user.

Me too.

Post by Florent B
What I liked in TextSecure was... encryption.

Great, well it's still there and working fine.

Post by Florent B
With last release, no more Encrypted SMS.

That's right. Too many support queries from users who had issues with it,
it only works Android<->Android. It's continued inclusion is holding the
project's goals back.

Post by Florent B
What is TextSecure for, now ?

TextSecure is still a way to send encrypted messages to other users using
TextSecure. (The same as it always ways)
TextSecure can now send messages to iOS devices running Signal (This
wasn't possible if you send an encrypted SMS, iPhone's don't allow another
app to read SMS messages)
TextSecure is still a way to ensure that only you can read the SMS
messages on your Android device (The same as it always was)
TextSecure is still open source, auditable and trustable (The same as it
always was)
TextSecure is no longer able to send the encrypted messages via the
SMS/MMS channel, only via the data channel. If that's something you must
have, then yes, TextSecure is sadly no longer for you.

Post by Florent B
So, I WAS a TextSecure user. bye

Goodbye :(

Post by Florent B
Florent

Tim

[Sam Lanning]

Hi Leandro

On Wed, Mar 25, 2015 at 6:18 PM, Leandro Salvador

Post by Leandro Salvador
Hi Angel! Cool! =)
A GitHub's newbie question: when you fork a project, is it possible to
track/audit the changes considering the fork moment as the start point of
the new project? Securecom Text apparently erased their history and isn't
possible to audit the changes between the two projects (TextSecure and
SecurecomText)

SMSSecure (https://github.com/SMSSecure/SMSSecure) is a separate fork
of TextSecure which seemed to happen around the 18th March, and they
kept git history and seem to be merging in upstream changes as well.
It's just not out on the app store yet unfortunately. Seeing the
changes these guys have made is very easy.

Securecom-Text (https://github.com/Securecom/Securecom-Text/), seems
to be a separate attempt at a fork, and it does seem somewhat more
fishy and less active. SOmeone started an issue on this repo asking
maybe these guys to consider working with SMS Secure
(https://github.com/Securecom/Securecom-Text/issues/5), and they just
closed the issue without comment. It is possible to compare
Securecom-Text with TextSecure, but it is not particularly easy, and
there is no well defined point in TextSecure's commit history that we
can compare against, where we know the changes will be the least, and
even then the changes and what has been done will not be explained, it
is likely to be one big diff.

Cheers,
Sam.

[Leandro Salvador]

Thanks a lot Sam! =)

Sharing Angels' answer:

---------- Mensagem encaminhada ----------
De: "Angel Stoleski" <***@gmail.com>
Data: 25/03/2015 18:27
Assunto: Hello

Yes you can track in the historySMSSecure is forked by people who need

privacy not some commercial company like securecom which I dont trust but
since its opensource you can audit the program (although it will take some
time to look into the code) or blackboxit the app. Are you a programmer or ?

Hi Leandro
On Wed, Mar 25, 2015 at 6:18 PM, Leandro Salvador

Post by Leandro Salvador
Hi Angel! Cool! =)
A GitHub's newbie question: when you fork a project, is it possible to
track/audit the changes considering the fork moment as the start point of
the new project? Securecom Text apparently erased their history and isn't
possible to audit the changes between the two projects (TextSecure and
SecurecomText)

SMSSecure (https://github.com/SMSSecure/SMSSecure) is a separate fork
of TextSecure which seemed to happen around the 18th March, and they
kept git history and seem to be merging in upstream changes as well.
It's just not out on the app store yet unfortunately. Seeing the
changes these guys have made is very easy.
Securecom-Text (https://github.com/Securecom/Securecom-Text/), seems
to be a separate attempt at a fork, and it does seem somewhat more
fishy and less active. SOmeone started an issue on this repo asking
maybe these guys to consider working with SMS Secure
(https://github.com/Securecom/Securecom-Text/issues/5), and they just
closed the issue without comment. It is possible to compare
Securecom-Text with TextSecure, but it is not particularly easy, and
there is no well defined point in TextSecure's commit history that we
can compare against, where we know the changes will be the least, and
even then the changes and what has been done will not be explained, it
is likely to be one big diff.
Cheers,
Sam.