What is a "Secure Message"?
A secure message Secure Message is a text message Short Text Message that can be sent and received by securely using PrivateGSM. Secure Message uses Messages share the same communication infrastructure of the Secure Voice communication to exchange data: provided used for secure voice. EVSS do not relay at all on Apple Push Notification or Google Cloud Messaging, in order to protect users' security:
- Server Authentication by SSL certificate.
- HTTPS and SIP over TLS protocols to exchange data
It's possible to send just text messages, but as PrivateGSM supports UNICODE and emoji character set, you can add emoticon icons as well.
| Warning |
|---|
BlackBerry platform does not support Emoji and thus cannot use them both for writing or reading. This is an operating system limitation and it's not recoverable. |
The maximum length of a single message is 160 character, so the input box refuses to let you write more than 160 chars.
| Note |
|---|
Please note there's no concatenation for Secure Messages. If you need to send a message that is longer than 160 characters, then you need to split it in more than one message by yourself. |
- data in encrypted way.
Secure Messages are text only, thus no attachments are provided. Maximum length of a Secure Message is 160 characters.
How does a Secure Message work?
When a customer user chooses to send a Secure Message, it triggers an HTTP HTTPS POST request in his client towards PrivateServer which plays a "store-and-forward" role. As . If recipient is online, Secure Message is immediately delivered. Otherwise it is stored temporarily in PrivateServer up to 3 days before expiring: as soon as the receiver recipient pops up online, PrivateServer delivers the Secure Message.
| Info |
|---|
At current state of development, message encryption is granted on the server for the storing period by an internal key. Future development will implement asymmetric key encryption side-to-side (PGP like, actually)Security model provided is end-to-site: message are protected during transport from wiretapping by TLS. Local temporary storage is encrypted with server key. |
Delivery is performed by SIP over TLS protocol, so as you can see the whole end-to-end path is encrypted and as the message is stored after a local encryption on the server, then there's (almost) no way of deciphering it.
Send
...
Secure
...
Messages
It's possible to write Secure Messages to other parties both by answering them or by writing for your own initiative. In the first case you would probably use the "Contact's History " view, in the latter you would use the "Contacts" list insteadContact's details view instead.
| Note |
|---|
Since the "History" lists all the communication attempted or happened on your PrivateGSM, it's possible to start a conversation using "History" as well, eg: answering to a missed call by a Secure Message or just using one event conveniently. |
Sending Secure Messages from "History" view
Each platform let you reach the "History" list by different names:
| Platform | "History" icon |
|---|---|
| Android |  |
| BlackBerry |  |
| iPhone |  |
Once you reached the history view, you can get an overall look of the activities occurred on your PrivateGSM:
...
...
...
Each item listed in "History" can be further detailed by selecting it and clicking on it.
...
...
...
Of course if the History item is about a call you'll read date, time and number of attempts performed by you or your party. Else, if it's about messages, you'll be able to read what your party wrote you about.
| Warning |
|---|
Please remember that once you read a Secure Message it starts to expire and after 15 minutes you won't be able to read its content anymore! |
As you can see in figure
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
| Typing a new Secure Message in history view (BlackBerry) | Typing a new Secure Message in history view (iPhone) | Typing a new Secure Message in history view (Android) | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
...
| Info |
|---|
Please note that by convention, your outgoing communications are placed on the right side of the screen, while the incoming ones by the chosen contact are placed on the left of the screen. |
| "Send" button | Platform | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| iPhone | |||||||||
| BlackBerry | |||||||||
| Android |
You can send your new message pressing the proper "Send" button in the User interface if you're on Android or iPhone, else on BlackBerry you just use the "Enter" key in your keyboard.
Sending Secure Messages from "
...
Contact's Detail"
...
As stated before, Secure Messages are also available from "Contacts" view which is probably the best way to start a conversation via text messages.
...
Obviously first thing it to reach the contact you want to write to. Please refer to Performing a secure call with PrivateGSM.
Central button on BlackBerry keyboard | "info" icon in iPhone | "info" icon in Android | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
...
|
Once you reached the specific number of your peer contact, then you can open his contact's history by pressing the "info" icon in Android and iPhone or just pressing the central button on the keyboard in BlackBerry (please check Xref AnchorName bb_
...
central_
...
button
...
You have to select an account from the list shown in ,
and Xref AnchorName iphone_info_icon Xref AnchorName
| Xref | ||
|---|---|---|
|
Once you select the desired phone number of the account you want to send Secure Messages to, then you get the view shown in
| Xref | ||
|---|---|---|
|
Secure Messages status icons and known limitations
Each Secure Message is displayed with an icon showing its status. Available Statuses/icons are
).android_info_icon
You'll get exactly the same view shown in History (detailed event view).
| Info |
|---|
Please note that by convention your outgoing communications are placed on the right side of the screen, while the incoming ones by the chosen contact are placed on the left of the screen. |
So you can now type your message, just as in
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
| Xref | ||
|---|---|---|
|
Receive a Secure Message
Obviously a Secure Message can be received as it can be sent. In this case a specific notification is raised by PrivateGSM using system's notifications.
iPhone locked | PrivateGSM in background | Once you open the application |
|---|---|---|
new Secure Message notification is shown | PrivateGSM shows an event notification on its icon | "Recent" icon shows how many events occurred. Clicking on "Recent" shows "History" list with event item in bold. |
 |  |  |
| BlackBerry locked | Click on system's notification area | Click on PrivateGSM item |
|---|---|---|
Sound and vibration notify a new event. Once unlocked "new message" icon is shown in notification area | When you drop down the event list, PrivateGSM item shows the "new message" icon and you can click on it. | You got redirected directly to "History" view where "Message received" event is bolded. |
 |  |  |
| Android locked | Click on system's notification area | Click on PrivateGSM item |
|---|---|---|
Sound and vibration notify a new event. If you had a model equipped with coloured led, then it would lit. Once unlocked, "new message" icon is shown in notification area | When you drop down the event list, PrivateGSM item shows the "new message" icon and some details about the sender. | Once you clicked on PrivateGSM item in event list, you got redirected directly to "History" view where the "received message" event is bolded. |
 |  |  |
| Info |
|---|
If just one message has been received, then clicking on the notification would lead you directly to the event detail where you'll be able to read the message. |
As shown above each platform shows the event notification differently, according to the underlying operating system behaviour.
Secure Messages compared to SMSs
Secure Messages provide a user experience very similar to SMS, adding security and with some minor differences. Some current constraints will be relaxed in next versions.
Secure Messages look just like clear text messages but they are not. Instead they are a sophisticated way for writing each other and their complex architecture implies some bounds:
- There's no chat group / no chat room feature: you can send Secure Messages only to one peer at the time.
- Exception made for BlackBerry, you can use Emoji characters to spice up your messages
| Info |
|---|
To use Emoji set it's mandatory to enable this character set on your device. This is an Operating System option thus please refer to your device manual. |
- You cannot attach anything to a Secure Message: Secure Messages are actually text only.
- Secure Message length is fixed to a maximum of 160 characters.
- Each Secure Message has a time validity, after which it expires. Expiration means that the Secure Message content is no longer readable and it's gone for good. Instead of message content you'd rather read "Message received" or "Message sent".
| BlackBerry expired Secure Message | iPhone expired Secure Message | Android expired Secure Message |
|---|---|---|
 |  |  |
Each time you send a Secure Message you can see a status icon appearing on its side. Here follows an explanation of each icon along with its status name and meaning:
| Icon | Description | Meaning | Timeouts and general behaviour |
|---|---|---|---|
Sending Message | PrivateGSM is actually trying to send the Secure Message to its recipient via PrivateServer | If there is some network issue, then PrivateGSM starts the retry procedure: it tries to send 5 times the message to PrivateServer. If it fails at the fifth try (5 * TLSTimeout = 60 secs), then the message remains in the client queue waiting for one of the following triggers:
If more than 12 hours passed and the message is still in client queue waiting to be sent, then the message expires: a "Send error" notification is fired by PrivateGSM and the message is removed from sender local queue
| |
 | Message Enqueued | PrivateGSM was able to send the Secure Message which now is in the queue of PrivateServer encrypted. PrivateServer tries to deliver it to its destinationhas been enqueued in PrivateServer encrypted storage and will be delivered to recipient as soon as possible. | If delivery is not possible because the peer if offline, PrivateServer retries as soon as recipient registers for up to an expiration period (72h), before removing them definitely from the database. If the user is online but there is a network issue, the server try to deliver the message 5 times every 30 seconds. If at the fifth attempt the network issue is still present, the retry procedure will be stopped and the message will be sent when the user will return online. |
| Message Delivered | PrivateServer was able to deliver the Secure Message has been delivered to its recipient. The message could be read as recipient's device, who could have read it or not. | None | |
| Error sending Message | This status is a fall back for any other one and it's triggered both by timeouts and error responses. | None |
Receive a secure message
sdgsdg
Features and limits (no chat group, no chat rooms, sì a emoji->indica come attivarlo su iphone e android, status della consegna del messaggio, tempi di validità del messaggio, no attach, no autosplit, max lenght = 160 chars)
sdfds
| Info |
|---|
To use Emoji set it's mandatory to enable it on your device. This is an Operating System option thus please refer to your device manual. |
You can also communicate by text messages using the Private Message System (henceforth PMS). PMS provides Private Text Message (henceforth PTM) which does relay on the very same security infrastructure the voice calls do.
| Navbar |
|---|