mirrors/signal-desktop
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
signal-desktop/libtextsecure/api.js

459 lines
17 KiB
JavaScript
Raw Normal View History

Remove erroneous license file and headers We only use GPLV3 around here. // FREEBIE
2015-09-07 21:53:43 +00:00
/*
* vim: ts=4:sw=4:expandtab
LGPL license (I'd like to be an axolotl/TS JS lib in the future)
2014-05-04 06:34:13 +00:00
*/
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
var TextSecureServer = (function() {
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
'use strict';
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
function validateResponse(response, schema) {
try {
for (var i in schema) {
switch (schema[i]) {
case 'object':
case 'string':
case 'number':
if (typeof response[i] !== schema[i]) {
return false;
}
break;
}
}
} catch(ex) {
return false;
}
return true;
}
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
function createSocket(url) {
Support pass-through proxies with HTTPS_PROXY env var (#1878) We've simplified; HTTPS_PROXY or https_proxy is used for all requests. We also require that only our self-signed certificates are used for secure traffic. That rules out all SSL-terminating MITM proxies, since we don't trust their root certificate. Once we're sure that this system works for people, we'll improve config on MacOS and Windows.
2017-12-08 18:38:01 +00:00
var proxyUrl = window.config.proxyUrl;
Add proxy support based on environment variables (#1855) We pull proxy settings from environment variables: - HTTPS_PROXY for sending, profile pulls, and attachment download/upload - WSS_PROXY for connecting to the websocket for receiving messages - ALL_PROXY to provide one server for both More details on our proxy handling: - https://github.com/Rob--W/proxy-from-env#environment-variables - https://github.com/TooTallNate/node-proxy-agent This is the natural way of things for Linux. My understanding is that most proxies on MacOS are system-wide and transparent, so it's not so urgent. But Windows will likely require further UI for configuration. Will need to do some testing with Windows users.
2017-12-04 23:35:50 +00:00
var requestOptions;
if (proxyUrl) {
requestOptions = {
Support pass-through proxies with HTTPS_PROXY env var (#1878) We've simplified; HTTPS_PROXY or https_proxy is used for all requests. We also require that only our self-signed certificates are used for secure traffic. That rules out all SSL-terminating MITM proxies, since we don't trust their root certificate. Once we're sure that this system works for people, we'll improve config on MacOS and Windows.
2017-12-08 18:38:01 +00:00
ca: window.config.certificateAuthorities,
agent: new ProxyAgent(proxyUrl),
Add proxy support based on environment variables (#1855) We pull proxy settings from environment variables: - HTTPS_PROXY for sending, profile pulls, and attachment download/upload - WSS_PROXY for connecting to the websocket for receiving messages - ALL_PROXY to provide one server for both More details on our proxy handling: - https://github.com/Rob--W/proxy-from-env#environment-variables - https://github.com/TooTallNate/node-proxy-agent This is the natural way of things for Linux. My understanding is that most proxies on MacOS are system-wide and transparent, so it's not so urgent. But Windows will likely require further UI for configuration. Will need to do some testing with Windows users.
2017-12-04 23:35:50 +00:00
};
} else {
requestOptions = {
ca: window.config.certificateAuthorities,
};
}
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
return new nodeWebSocket(url, null, null, null, requestOptions);
}
window.setImmediate = nodeSetImmediate;
Automatically retry failed http requests If we failed to reach the server, wait a second and try again up to 3 times. // FREEBIE
2015-10-11 02:07:00 +00:00
function promise_ajax(url, options) {
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
return new Promise(function (resolve, reject) {
if (!url) {
url = options.host + '/' + options.path;
}
console.log(options.type, url);
Increase web request timeout, drop failed delivery receipts (#1699) Increase web request timeout, drop failed delivery receipts, export error logging
2017-11-07 18:49:10 +00:00
var timeout = typeof options.timeout !== 'undefined' ? options.timeout : 10000;
Add 5s timeout for all requests but attachment up/down, avatar (#1584) * Remove hang workaround in api.js since we have global workaround * Add 5s timeout for all requests exept attachment up/down, avatar
2017-10-21 00:02:44 +00:00
Support pass-through proxies with HTTPS_PROXY env var (#1878) We've simplified; HTTPS_PROXY or https_proxy is used for all requests. We also require that only our self-signed certificates are used for secure traffic. That rules out all SSL-terminating MITM proxies, since we don't trust their root certificate. Once we're sure that this system works for people, we'll improve config on MacOS and Windows.
2017-12-08 18:38:01 +00:00
var proxyUrl = window.config.proxyUrl;
Add proxy support based on environment variables (#1855) We pull proxy settings from environment variables: - HTTPS_PROXY for sending, profile pulls, and attachment download/upload - WSS_PROXY for connecting to the websocket for receiving messages - ALL_PROXY to provide one server for both More details on our proxy handling: - https://github.com/Rob--W/proxy-from-env#environment-variables - https://github.com/TooTallNate/node-proxy-agent This is the natural way of things for Linux. My understanding is that most proxies on MacOS are system-wide and transparent, so it's not so urgent. But Windows will likely require further UI for configuration. Will need to do some testing with Windows users.
2017-12-04 23:35:50 +00:00
var agent;
if (proxyUrl) {
agent = new ProxyAgent(proxyUrl);
}
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
var fetchOptions = {
method: options.type,
body: options.data || null,
headers: { 'X-Signal-Agent': 'OWD' },
Add proxy support based on environment variables (#1855) We pull proxy settings from environment variables: - HTTPS_PROXY for sending, profile pulls, and attachment download/upload - WSS_PROXY for connecting to the websocket for receiving messages - ALL_PROXY to provide one server for both More details on our proxy handling: - https://github.com/Rob--W/proxy-from-env#environment-variables - https://github.com/TooTallNate/node-proxy-agent This is the natural way of things for Linux. My understanding is that most proxies on MacOS are system-wide and transparent, so it's not so urgent. But Windows will likely require further UI for configuration. Will need to do some testing with Windows users.
2017-12-04 23:35:50 +00:00
agent: agent,
Support pass-through proxies with HTTPS_PROXY env var (#1878) We've simplified; HTTPS_PROXY or https_proxy is used for all requests. We also require that only our self-signed certificates are used for secure traffic. That rules out all SSL-terminating MITM proxies, since we don't trust their root certificate. Once we're sure that this system works for people, we'll improve config on MacOS and Windows.
2017-12-08 18:38:01 +00:00
ca: options.certificateAuthorities,
Add proxy support based on environment variables (#1855) We pull proxy settings from environment variables: - HTTPS_PROXY for sending, profile pulls, and attachment download/upload - WSS_PROXY for connecting to the websocket for receiving messages - ALL_PROXY to provide one server for both More details on our proxy handling: - https://github.com/Rob--W/proxy-from-env#environment-variables - https://github.com/TooTallNate/node-proxy-agent This is the natural way of things for Linux. My understanding is that most proxies on MacOS are system-wide and transparent, so it's not so urgent. But Windows will likely require further UI for configuration. Will need to do some testing with Windows users.
2017-12-04 23:35:50 +00:00
timeout: timeout,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
};
Remove libtextsecure's jquery dependency Use only the finest, hand-crafted, artisanal XMLHttpRequests.
2015-03-25 00:04:41 +00:00
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
if (fetchOptions.body instanceof ArrayBuffer) {
// node-fetch doesn't support ArrayBuffer, only node Buffer
var contentLength = fetchOptions.body.byteLength;
fetchOptions.body = nodeBuffer.from(fetchOptions.body);
Add signal agent to server requests // FREEBIE
2015-12-04 18:45:53 +00:00
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
// node-fetch doesn't set content-length like S3 requires
fetchOptions.headers["Content-Length"] = contentLength;
}
DRY up Promise creation in api.js Since calls to ajax() are always wrapped in promises, we can internalize that pattern in the ajax function itself. // FREEBIE
2015-07-13 18:52:49 +00:00
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
if (options.user && options.password) {
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
fetchOptions.headers["Authorization"] =
"Basic " + btoa(getString(options.user) + ":" + getString(options.password));
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
}
if (options.contentType) {
fetchOptions.headers["Content-Type"] = options.contentType;
}
window.nodeFetch(url, fetchOptions).then(function(response) {
var resultPromise;
Fix json parsing exceptions obscuring server errors (#1605) I got a 413 (Rate limit exceeded) error from the server while fetching prekeys. The client tried to parse the response as json since we expect json from the prekey endpoint, which threw an exception because the response was not json. This change prevents us from treating the response as json unless it has the Content-Type header set accordingly. If for some reason, the client and server disagree on whether the response should be or is json, we'll default to treating it as text. // FREEBIE
2017-10-24 22:54:46 +00:00
if (options.responseType === 'json'
&& response.headers.get('Content-Type') === 'application/json') {
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
resultPromise = response.json();
} else if (options.responseType === 'arraybuffer') {
resultPromise = response.buffer();
Fix json parsing exceptions obscuring server errors (#1605) I got a 413 (Rate limit exceeded) error from the server while fetching prekeys. The client tried to parse the response as json since we expect json from the prekey endpoint, which threw an exception because the response was not json. This change prevents us from treating the response as json unless it has the Content-Type header set accordingly. If for some reason, the client and server disagree on whether the response should be or is json, we'll default to treating it as text. // FREEBIE
2017-10-24 22:54:46 +00:00
} else {
resultPromise = response.text();
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
}
return resultPromise.then(function(result) {
if (options.responseType === 'arraybuffer') {
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
result = result.buffer.slice(
result.byteOffset,
result.byteOffset + result.byteLength
);
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
}
if (options.responseType === 'json') {
if (options.validateResponse) {
if (!validateResponse(result, options.validateResponse)) {
console.log(options.type, url, response.status, 'Error');
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
reject(HTTPError(
'promise_ajax: invalid response',
response.status,
result,
options.stack
));
DRY up Promise creation in api.js Since calls to ajax() are always wrapped in promises, we can internalize that pattern in the ajax function itself. // FREEBIE
2015-07-13 18:52:49 +00:00
}
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
}
}
Add 5s timeout for all requests but attachment up/down, avatar (#1584) * Remove hang workaround in api.js since we have global workaround * Add 5s timeout for all requests exept attachment up/down, avatar
2017-10-21 00:02:44 +00:00
if (0 <= response.status && response.status < 400) {
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
console.log(options.type, url, response.status, 'Success');
resolve(result, response.status);
} else {
console.log(options.type, url, response.status, 'Error');
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
reject(HTTPError(
'promise_ajax: error response',
response.status,
result,
options.stack
));
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
}
});
}).catch(function(e) {
console.log(options.type, url, 0, 'Error');
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
var stack = e.stack + '\nInitial stack:\n' + options.stack;
reject(HTTPError('promise_ajax catch', 0, e.toString(), stack));
DRY up Promise creation in api.js Since calls to ajax() are always wrapped in promises, we can internalize that pattern in the ajax function itself. // FREEBIE
2015-07-13 18:52:49 +00:00
});
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
});
Move throwHumanError to api.js It is only used there.
2015-04-30 19:13:04 +00:00
}
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
function retry_ajax(url, options, limit, count) {
count = count || 0;
limit = limit || 3;
count++;
return promise_ajax(url, options).catch(function(e) {
if (e.name === 'HTTPError' && e.code === -1 && count < limit) {
Automatically retry failed http requests If we failed to reach the server, wait a second and try again up to 3 times. // FREEBIE
2015-10-11 02:07:00 +00:00
return new Promise(function(resolve) {
setTimeout(function() {
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
resolve(retry_ajax(url, options, limit, count));
}, 1000);
Automatically retry failed http requests If we failed to reach the server, wait a second and try again up to 3 times. // FREEBIE
2015-10-11 02:07:00 +00:00
});
} else {
throw e;
}
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
});
}
Automatically retry failed http requests If we failed to reach the server, wait a second and try again up to 3 times. // FREEBIE
2015-10-11 02:07:00 +00:00
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
function ajax(url, options) {
options.stack = new Error().stack; // just in case, save stack here.
return retry_ajax(url, options);
Automatically retry failed http requests If we failed to reach the server, wait a second and try again up to 3 times. // FREEBIE
2015-10-11 02:07:00 +00:00
}
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
function HTTPError(message, code, response, stack) {
Convert throwHumanError to custom error type Now with 200% more helpful stack traces. // FREEBIE
2015-07-10 18:28:47 +00:00
if (code > 999 || code < 100) {
code = -1;
}
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
var e = new Error(message + '; code: ' + code);
Convert throwHumanError to custom error type Now with 200% more helpful stack traces. // FREEBIE
2015-07-10 18:28:47 +00:00
e.name = 'HTTPError';
e.code = code;
Log more info w/http errors, resilient to invalid group members (#1968) * api.js: HttpError now preserves more of original error info * Allow invalid conversation to be added to ConversationController If a number we don't believe is valid comes in as part of a group, we fall apart. We event prevent display of that conversation. Because we have 'isValid()' protections in place for the places we create contacts from user input in desktop (the search bar), we can temporarily add an invalid contact to our collection (not saving it to the database) to unblock this group scenario. Still investigating what kind of phone number is valid in a mobile app but not valid for us. * Finish the debuggable error support * Fix logging in the case of an invalid number
2018-01-13 00:19:26 +00:00
e.stack += '\nOriginal stack:\n' + stack;
Convert throwHumanError to custom error type Now with 200% more helpful stack traces. // FREEBIE
2015-07-10 18:28:47 +00:00
if (response) {
e.response = response;
}
return e;
Move throwHumanError to api.js It is only used there.
2015-04-30 19:13:04 +00:00
}
Remove libtextsecure's jquery dependency Use only the finest, hand-crafted, artisanal XMLHttpRequests.
2015-03-25 00:04:41 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
var URL_CALLS = {
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
accounts : "v1/accounts",
devices : "v1/devices",
keys : "v2/keys",
Support for server endpoint to set signed key
2017-02-16 02:03:23 +00:00
signed : "v2/keys/signed",
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
messages : "v1/messages",
Add support for getProfile to TextSecureServer // FREEBIE
2017-05-24 20:17:20 +00:00
attachment : "v1/attachments",
profile : "v1/profile"
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
};
tabstabstabstabstabs
2014-03-22 22:45:01 +00:00
Profiles (#1453) * Add AES-GCM encryption for profiles With tests. * Add profileKey to DataMessage protobuf // FREEBIE * Decrypt and save profile names // FREEBIE * Save incoming profile keys * Move pad/unpad to crypto module // FREEBIE * Support fetching avatars from the cdn // FREEBIE * Translate failed authentication errors When AES-GCM authentication fails, webcrypto returns a very generic error. The same error is thrown for invalid length inputs, but our earlier checks in decryptProfile should rule out those failure modes and leave us safe to assume that we either had bad ciphertext or the wrong key. // FREEBIE * Handle profile avatars (wip) and log decrypt errors // FREEBIE * Display profile avatars Synced contact avatars will still override profile avatars. * Display profile names in convo list Only if we don't have a synced contact name. // FREEBIE * Make cdn url an environment config Use different ones for staging and production // FREEBIE * Display profile name in conversation header * Display profile name in group messages * Update conversation header if profile avatar changes // FREEBIE * Style profile names small with ~ * Save profileKeys from contact sync messages // FREEBIE * Save profile keys from provisioning messages For standalone accounts, generate a random profile key. // FREEBIE * Special case for one-time sync of our profile key Android will use a contact sync message to sync a profile key from Android clients who have just upgraded and generated their profile key. Normally we should receive this data in a provisioning message. // FREEBIE * Infer profile sharing from synced data messages * Populate profile keys on outgoing messages Requires that `profileSharing` be set on the conversation. // FREEBIE * Support for the profile key update flag When receiving a message with this flag, don't init a message record, just process the profile key and move on. // FREEBIE * Display profile names in group member list * Refresh contact's profile on profile key changes // FREEBIE * Catch errors on profile save // FREEBIE * Save our own synced contact info Don't return early if we get a contact sync for our own number // FREEBIE
2017-09-11 16:50:35 +00:00
function TextSecureServer(url, username, password, cdn_url) {
Throw on bad server url // FREEBIE
2015-09-25 00:59:57 +00:00
if (typeof url !== 'string') {
throw new Error('Invalid server url');
}
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
this.url = url;
Profiles (#1453) * Add AES-GCM encryption for profiles With tests. * Add profileKey to DataMessage protobuf // FREEBIE * Decrypt and save profile names // FREEBIE * Save incoming profile keys * Move pad/unpad to crypto module // FREEBIE * Support fetching avatars from the cdn // FREEBIE * Translate failed authentication errors When AES-GCM authentication fails, webcrypto returns a very generic error. The same error is thrown for invalid length inputs, but our earlier checks in decryptProfile should rule out those failure modes and leave us safe to assume that we either had bad ciphertext or the wrong key. // FREEBIE * Handle profile avatars (wip) and log decrypt errors // FREEBIE * Display profile avatars Synced contact avatars will still override profile avatars. * Display profile names in convo list Only if we don't have a synced contact name. // FREEBIE * Make cdn url an environment config Use different ones for staging and production // FREEBIE * Display profile name in conversation header * Display profile name in group messages * Update conversation header if profile avatar changes // FREEBIE * Style profile names small with ~ * Save profileKeys from contact sync messages // FREEBIE * Save profile keys from provisioning messages For standalone accounts, generate a random profile key. // FREEBIE * Special case for one-time sync of our profile key Android will use a contact sync message to sync a profile key from Android clients who have just upgraded and generated their profile key. Normally we should receive this data in a provisioning message. // FREEBIE * Infer profile sharing from synced data messages * Populate profile keys on outgoing messages Requires that `profileSharing` be set on the conversation. // FREEBIE * Support for the profile key update flag When receiving a message with this flag, don't init a message record, just process the profile key and move on. // FREEBIE * Display profile names in group member list * Refresh contact's profile on profile key changes // FREEBIE * Catch errors on profile save // FREEBIE * Save our own synced contact info Don't return early if we get a contact sync for our own number // FREEBIE
2017-09-11 16:50:35 +00:00
this.cdn_url = cdn_url;
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
this.username = username;
this.password = password;
}
Work on auth error handling / reinstall
2015-06-19 22:32:25 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
TextSecureServer.prototype = {
constructor: TextSecureServer,
ajax: function(param) {
if (!param.urlParameters) {
param.urlParameters = '';
}
Add server fallback port 8443 // FREEBIE
2016-09-08 04:53:56 +00:00
return ajax(null, {
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
host : this.url,
path : URL_CALLS[param.call] + param.urlParameters,
type : param.httpType,
data : param.jsonData && textsecure.utils.jsonThing(param.jsonData),
contentType : 'application/json; charset=utf-8',
responseType : param.responseType,
user : this.username,
password : this.password,
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
validateResponse: param.validateResponse,
Add 5s timeout for all requests but attachment up/down, avatar (#1584) * Remove hang workaround in api.js since we have global workaround * Add 5s timeout for all requests exept attachment up/down, avatar
2017-10-21 00:02:44 +00:00
certificateAuthorities: window.config.certificateAuthorities,
timeout : param.timeout
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}).catch(function(e) {
var code = e.code;
if (code === 200) {
// happens sometimes when we get no response
// (TODO: Fix server to return 204? instead)
return null;
}
var message;
switch (code) {
case -1:
message = "Failed to connect to the server, please check your network connection.";
break;
case 413:
message = "Rate limit exceeded, please try again later.";
break;
case 403:
message = "Invalid code, please try again.";
break;
case 417:
// TODO: This shouldn't be a thing?, but its in the API doc?
message = "Number already registered.";
break;
case 401:
message = "Invalid authentication, most likely someone re-registered and invalidated our registration.";
break;
case 404:
Remove 'Textsecure' from error message in api.js
2015-11-13 18:15:03 +00:00
message = "Number is not registered.";
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
break;
default:
message = "The server rejected our query, please file a bug report.";
}
e.message = message
throw e;
});
},
Add support for getProfile to TextSecureServer // FREEBIE
2017-05-24 20:17:20 +00:00
getProfile: function(number) {
return this.ajax({
call : 'profile',
httpType : 'GET',
urlParameters : '/' + number,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : 'json',
Add support for getProfile to TextSecureServer // FREEBIE
2017-05-24 20:17:20 +00:00
});
},
Profiles (#1453) * Add AES-GCM encryption for profiles With tests. * Add profileKey to DataMessage protobuf // FREEBIE * Decrypt and save profile names // FREEBIE * Save incoming profile keys * Move pad/unpad to crypto module // FREEBIE * Support fetching avatars from the cdn // FREEBIE * Translate failed authentication errors When AES-GCM authentication fails, webcrypto returns a very generic error. The same error is thrown for invalid length inputs, but our earlier checks in decryptProfile should rule out those failure modes and leave us safe to assume that we either had bad ciphertext or the wrong key. // FREEBIE * Handle profile avatars (wip) and log decrypt errors // FREEBIE * Display profile avatars Synced contact avatars will still override profile avatars. * Display profile names in convo list Only if we don't have a synced contact name. // FREEBIE * Make cdn url an environment config Use different ones for staging and production // FREEBIE * Display profile name in conversation header * Display profile name in group messages * Update conversation header if profile avatar changes // FREEBIE * Style profile names small with ~ * Save profileKeys from contact sync messages // FREEBIE * Save profile keys from provisioning messages For standalone accounts, generate a random profile key. // FREEBIE * Special case for one-time sync of our profile key Android will use a contact sync message to sync a profile key from Android clients who have just upgraded and generated their profile key. Normally we should receive this data in a provisioning message. // FREEBIE * Infer profile sharing from synced data messages * Populate profile keys on outgoing messages Requires that `profileSharing` be set on the conversation. // FREEBIE * Support for the profile key update flag When receiving a message with this flag, don't init a message record, just process the profile key and move on. // FREEBIE * Display profile names in group member list * Refresh contact's profile on profile key changes // FREEBIE * Catch errors on profile save // FREEBIE * Save our own synced contact info Don't return early if we get a contact sync for our own number // FREEBIE
2017-09-11 16:50:35 +00:00
getAvatar: function(path) {
return ajax(this.cdn_url + '/' + path, {
type : "GET",
responseType: "arraybuffer",
contentType : "application/octet-stream",
Add 5s timeout for all requests but attachment up/down, avatar (#1584) * Remove hang workaround in api.js since we have global workaround * Add 5s timeout for all requests exept attachment up/down, avatar
2017-10-21 00:02:44 +00:00
certificateAuthorities: window.config.certificateAuthorities,
timeout: 0
Profiles (#1453) * Add AES-GCM encryption for profiles With tests. * Add profileKey to DataMessage protobuf // FREEBIE * Decrypt and save profile names // FREEBIE * Save incoming profile keys * Move pad/unpad to crypto module // FREEBIE * Support fetching avatars from the cdn // FREEBIE * Translate failed authentication errors When AES-GCM authentication fails, webcrypto returns a very generic error. The same error is thrown for invalid length inputs, but our earlier checks in decryptProfile should rule out those failure modes and leave us safe to assume that we either had bad ciphertext or the wrong key. // FREEBIE * Handle profile avatars (wip) and log decrypt errors // FREEBIE * Display profile avatars Synced contact avatars will still override profile avatars. * Display profile names in convo list Only if we don't have a synced contact name. // FREEBIE * Make cdn url an environment config Use different ones for staging and production // FREEBIE * Display profile name in conversation header * Display profile name in group messages * Update conversation header if profile avatar changes // FREEBIE * Style profile names small with ~ * Save profileKeys from contact sync messages // FREEBIE * Save profile keys from provisioning messages For standalone accounts, generate a random profile key. // FREEBIE * Special case for one-time sync of our profile key Android will use a contact sync message to sync a profile key from Android clients who have just upgraded and generated their profile key. Normally we should receive this data in a provisioning message. // FREEBIE * Infer profile sharing from synced data messages * Populate profile keys on outgoing messages Requires that `profileSharing` be set on the conversation. // FREEBIE * Support for the profile key update flag When receiving a message with this flag, don't init a message record, just process the profile key and move on. // FREEBIE * Display profile names in group member list * Refresh contact's profile on profile key changes // FREEBIE * Catch errors on profile save // FREEBIE * Save our own synced contact info Don't return early if we get a contact sync for our own number // FREEBIE
2017-09-11 16:50:35 +00:00
});
},
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
requestVerificationSMS: function(number) {
return this.ajax({
call : 'accounts',
httpType : 'GET',
urlParameters : '/sms/code/' + number,
});
},
requestVerificationVoice: function(number) {
return this.ajax({
call : 'accounts',
httpType : 'GET',
urlParameters : '/voice/code/' + number,
});
},
confirmCode: function(number, code, password, signaling_key, registrationId, deviceName) {
Add support for device name
2015-06-18 18:00:58 +00:00
var jsonData = {
signalingKey : btoa(getString(signaling_key)),
supportsSms : false,
fetchesMessages : true,
registrationId : registrationId,
};
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
var call, urlPrefix, schema, responseType;
Add support for device name
2015-06-18 18:00:58 +00:00
if (deviceName) {
jsonData.name = deviceName;
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
call = 'devices';
urlPrefix = '/';
schema = { deviceId: 'number' };
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType = 'json'
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
} else {
call = 'accounts';
urlPrefix = '/code/';
Add support for device name
2015-06-18 18:00:58 +00:00
}
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
this.username = number;
this.password = password;
return this.ajax({
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
call : call,
httpType : 'PUT',
urlParameters : urlPrefix + code,
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
jsonData : jsonData,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : responseType,
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
validateResponse : schema
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
});
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
},
getDevices: function(number) {
return this.ajax({
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
call : 'devices',
httpType : 'GET',
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
});
},
registerKeys: function(genKeys) {
var keys = {};
keys.identityKey = btoa(getString(genKeys.identityKey));
Add parens and line breaks // FREEBIE
2015-10-10 22:12:06 +00:00
keys.signedPreKey = {
keyId: genKeys.signedPreKey.keyId,
publicKey: btoa(getString(genKeys.signedPreKey.publicKey)),
signature: btoa(getString(genKeys.signedPreKey.signature))
};
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
keys.preKeys = [];
var j = 0;
Add parens and line breaks // FREEBIE
2015-10-10 22:12:06 +00:00
for (var i in genKeys.preKeys) {
keys.preKeys[j++] = {
keyId: genKeys.preKeys[i].keyId,
publicKey: btoa(getString(genKeys.preKeys[i].publicKey))
};
}
Add textsecure.refreshKeys This helper checks the server for the number of remaining prekeys, then generates more if there are fewer than 10 remaining. // FREEBIE
2015-04-28 23:26:41 +00:00
Remove api TODO comments // FREEBIE
2015-11-04 18:31:50 +00:00
// This is just to make the server happy
// (v2 clients should choke on publicKey)
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
keys.lastResortKey = {keyId: 0x7fffFFFF, publicKey: btoa("42")};
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
return this.ajax({
call : 'keys',
httpType : 'PUT',
jsonData : keys,
});
},
Support for server endpoint to set signed key
2017-02-16 02:03:23 +00:00
setSignedPreKey: function(signedPreKey) {
return this.ajax({
call : 'signed',
httpType : 'PUT',
jsonData : {
keyId: signedPreKey.keyId,
publicKey: btoa(getString(signedPreKey.publicKey)),
signature: btoa(getString(signedPreKey.signature))
}
});
},
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
getMyKeys: function(number, deviceId) {
return this.ajax({
call : 'keys',
httpType : 'GET',
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : 'json',
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
validateResponse : {count: 'number'}
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}).then(function(res) {
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
return res.count;
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
});
},
getKeysForNumber: function(number, deviceId) {
if (deviceId === undefined)
deviceId = "*";
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
return this.ajax({
call : 'keys',
httpType : 'GET',
urlParameters : "/" + number + "/" + deviceId,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : 'json',
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
validateResponse : {identityKey: 'string', devices: 'object'}
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}).then(function(res) {
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
if (res.devices.constructor !== Array) {
throw new Error("Invalid response");
}
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
res.identityKey = StringView.base64ToBytes(res.identityKey);
Use forEach instead of loop // FREEBIE
2016-03-13 21:15:16 +00:00
res.devices.forEach(function(device) {
Support for undefined preKey
2017-02-09 06:23:42 +00:00
if ( !validateResponse(device, {signedPreKey: 'object'}) ||
!validateResponse(device.signedPreKey, {publicKey: 'string', signature: 'string'}) ) {
throw new Error("Invalid signedPreKey");
}
if ( device.preKey ) {
if ( !validateResponse(device, {preKey: 'object'}) ||
!validateResponse(device.preKey, {publicKey: 'string'})) {
throw new Error("Invalid preKey");
}
device.preKey.publicKey = StringView.base64ToBytes(device.preKey.publicKey);
Validate json responses Perform lightweight validation on json responses from the server. Ensure that the attributes we depend on have the right type. // FREEBIE
2015-11-25 20:07:23 +00:00
}
Use forEach instead of loop // FREEBIE
2016-03-13 21:15:16 +00:00
device.signedPreKey.publicKey = StringView.base64ToBytes(device.signedPreKey.publicKey);
device.signedPreKey.signature = StringView.base64ToBytes(device.signedPreKey.signature);
});
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
return res;
});
},
Feature: Blue check marks for read messages if opted in (#1489) * Refactor delivery receipt event handler * Rename the delivery receipt event For less ambiguity with read receipts. * Rename synced read event For less ambiguity with read receipts from other Signal users. * Add support for incoming receipt messages Handle ReceiptMessages, which may include encrypted delivery receipts or read receipts from recipients of our sent messages. // FREEBIE * Rename ReadReceipts to ReadSyncs * Render read messages with blue double checks * Send read receipts to senders of incoming messages // FREEBIE * Move ReadSyncs to their own file // FREEBIE * Fixup old comments on read receipts (now read syncs) And some variable renaming for extra clarity. // FREEBIE * Add global setting for read receipts Don't send read receipt messages unless the setting is enabled. Don't process read receipts if the setting is disabled. // FREEBIE * Sync read receipt setting from mobile Toggling this setting on your mobile device should sync it to Desktop. When linking, use the setting in the provisioning message. // FREEBIE * Send receipt messages silently Avoid generating phantom messages on ios // FREEBIE * Save recipients on the outgoing message models For accurate tracking and display of sent/delivered/read state, even if group membership changes later. // FREEBIE * Fix conversation type in profile key update handling // FREEBIE * Set recipients on synced sent messages * Render saved recipients in message detail if available For older messages, where we did not save the intended set of recipients at the time of sending, fall back to the current group membership. // FREEBIE * Record who has been successfully sent to // FREEBIE * Record who a message has been delivered to * Invert the not-clickable class * Fix readReceipt setting sync when linking * Render per recipient sent/delivered/read status In the message detail view for outgoing messages, render each recipient's individual sent/delivered/read status with respect to this message, as long as there are no errors associated with the recipient (ie, safety number changes, user not registered, etc...) since the error icon is displayed in that case. *Messages sent before this change may not have per-recipient status lists and will simply show no status icon. // FREEBIE * Add configuration sync request Send these requests in a one-off fashion when: 1. We have just setup from a chrome app import 2. We have just upgraded to read-receipt support // FREEBIE * Expose sendRequestConfigurationSyncMessage // FREEBIE * Fix handling of incoming delivery receipts - union with array FREEBIE
2017-10-04 22:28:43 +00:00
sendMessages: function(destination, messageArray, timestamp, silent) {
Refactor messageSender/OutgoingMessage Move encrypt and transmit to OutgoingMessage Restore per-number queueing to messageSender // FREEBIE
2015-11-17 20:00:41 +00:00
var jsonData = { messages: messageArray, timestamp: timestamp};
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
Feature: Blue check marks for read messages if opted in (#1489) * Refactor delivery receipt event handler * Rename the delivery receipt event For less ambiguity with read receipts. * Rename synced read event For less ambiguity with read receipts from other Signal users. * Add support for incoming receipt messages Handle ReceiptMessages, which may include encrypted delivery receipts or read receipts from recipients of our sent messages. // FREEBIE * Rename ReadReceipts to ReadSyncs * Render read messages with blue double checks * Send read receipts to senders of incoming messages // FREEBIE * Move ReadSyncs to their own file // FREEBIE * Fixup old comments on read receipts (now read syncs) And some variable renaming for extra clarity. // FREEBIE * Add global setting for read receipts Don't send read receipt messages unless the setting is enabled. Don't process read receipts if the setting is disabled. // FREEBIE * Sync read receipt setting from mobile Toggling this setting on your mobile device should sync it to Desktop. When linking, use the setting in the provisioning message. // FREEBIE * Send receipt messages silently Avoid generating phantom messages on ios // FREEBIE * Save recipients on the outgoing message models For accurate tracking and display of sent/delivered/read state, even if group membership changes later. // FREEBIE * Fix conversation type in profile key update handling // FREEBIE * Set recipients on synced sent messages * Render saved recipients in message detail if available For older messages, where we did not save the intended set of recipients at the time of sending, fall back to the current group membership. // FREEBIE * Record who has been successfully sent to // FREEBIE * Record who a message has been delivered to * Invert the not-clickable class * Fix readReceipt setting sync when linking * Render per recipient sent/delivered/read status In the message detail view for outgoing messages, render each recipient's individual sent/delivered/read status with respect to this message, as long as there are no errors associated with the recipient (ie, safety number changes, user not registered, etc...) since the error icon is displayed in that case. *Messages sent before this change may not have per-recipient status lists and will simply show no status icon. // FREEBIE * Add configuration sync request Send these requests in a one-off fashion when: 1. We have just setup from a chrome app import 2. We have just upgraded to read-receipt support // FREEBIE * Expose sendRequestConfigurationSyncMessage // FREEBIE * Fix handling of incoming delivery receipts - union with array FREEBIE
2017-10-04 22:28:43 +00:00
if (silent) {
jsonData.silent = true;
}
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
return this.ajax({
call : 'messages',
httpType : 'PUT',
urlParameters : '/' + destination,
jsonData : jsonData,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : 'json',
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
});
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
},
getAttachment: function(id) {
return this.ajax({
call : 'attachment',
httpType : 'GET',
urlParameters : '/' + id,
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
responseType : 'json',
Add 5s timeout for all requests but attachment up/down, avatar (#1584) * Remove hang workaround in api.js since we have global workaround * Add 5s timeout for all requests exept attachment up/down, avatar
2017-10-21 00:02:44 +00:00
validateResponse : {location: 'string'},
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}).then(function(response) {
return ajax(response.location, {
Fix timeouts // FREEBIE
2017-10-23 16:07:56 +00:00
timeout : 0,
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
type : "GET",
responseType: "arraybuffer",
contentType : "application/octet-stream"
});
Validate attachment urls // FREEBIE
2015-11-24 20:40:00 +00:00
}.bind(this));
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
},
putAttachment: function(encryptedBin) {
return this.ajax({
Move to node fetch API for web requests instead of XHR (#1552) * Use node-fetch instead of xhr * Remove XMLHttpRequest.js // FREEBIE * Avoid calling json() on non json responses Previously we would catch and swallow JSON parsing errors resulting from an empty response, though empty responses are normal from a few endpoints, like requesting sms or voice registration codes. Since the JSON parsing call is now handled internally by node-fetch, we have to keep closer track of our expected response type to avoid throwing an exception. // FREEBIE
2017-10-20 22:52:02 +00:00
call : 'attachment',
httpType : 'GET',
responseType : 'json',
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}).then(function(response) {
return ajax(response.location, {
Fix timeouts // FREEBIE
2017-10-23 16:07:56 +00:00
timeout : 0,
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
type : "PUT",
contentType : "application/octet-stream",
data : encryptedBin,
processData : false,
}).then(function() {
Stop parsing attachment ids from attachment urls See 2111294 Attachment ids are now available in string form from the server response to `putAttachment`. // FREEBIE
2017-03-10 18:41:50 +00:00
return response.idString;
Validate attachment urls // FREEBIE
2015-11-24 20:40:00 +00:00
}.bind(this));
}.bind(this));
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
},
getMessageSocket: function() {
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
console.log('opening message socket', this.url);
return createSocket(this.url.replace('https://', 'wss://').replace('http://', 'ws://')
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
+ '/v1/websocket/?login=' + encodeURIComponent(this.username)
+ '&password=' + encodeURIComponent(this.password)
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
+ '&agent=OWD');
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
},
getProvisioningSocket: function () {
Certificate pinning via node XMLHttpRequest implementation (#1394) * Add certificate pinning on https service requests Make https requests to the server using node apis instead of browser apis, so we can specify our own CA list, which contains only our own CA. This protects us from MITM by a rogue CA. As a bonus, this let's us drop the use of non-standard ports and just use good ol' default 443 all the time, at least for http requests. // FREEBIE * Make certificateAuthorities an option on requests Modify node-based xhr implementation based on driverdan/node-XMLHttpRequest, adding support for setting certificate authorities on each request. This allows us to pin our master CA for requests to the server and cdn but not to the s3 attachment server, for instance. Also fix an exception when sending binary data in a request: it is submitted as an array buffer, and must be converted to a node Buffer since we are now using a node based request api. // FREEBIE * Import node-based xhr implementation Add a copy of https://github.com/driverdan/node-XMLHttpRequest@86ff70e, and expose it to the renderer in the preload script. In later commits this module will be extended to support custom certificate authorities. // FREEBIE * Support "arraybuffer" responseType on requests When fetching attachments, we want the result as binary data rather than a utf8 string. This lets our node-based XMLHttpRequest honor the responseType property if it is set on the xhr. Note that naively using the raw `.buffer` from a node Buffer won't work, since it is a reuseable backing buffer that is often much larger than the actual content defined by the Buffer's offset and length. Instead, we'll prepare a return buffer based on the response's content length header, and incrementally write chunks of data into it as they arrive. // FREEBIE * Switch to self-signed server endpoint * Log more error info on failed requests With the node-based xhr, relevant error info are stored in statusText and responseText when a request fails. // FREEBIE * Add node-based websocket w/ support for custom CA // FREEBIE * Support handling array buffers instead of blobs Our node-based websocket calls onmessage with an arraybuffer instead of a blob. For robustness (on the off chance we switch or update the socket implementation agian) I've kept the machinery for converting blobs to array buffers. // FREEBIE * Destroy all wacky server ports // FREEBIE
2017-09-01 15:58:58 +00:00
console.log('opening provisioning socket', this.url);
return createSocket(this.url.replace('https://', 'wss://').replace('http://', 'ws://')
+ '/v1/websocket/provisioning/?agent=OWD');
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
}
Standardize some whitespace The preferred style is 4 spaces.
2014-10-20 00:53:17 +00:00
};
Refactor TextSecureServer for storage Following the pattern from previous commit, let the server class accept a url and login credentials from the caller. Then integrate into MessageReceiver and AccountManager. // FREEBIE
2015-08-28 22:37:45 +00:00
return TextSecureServer;
})();
Reference in a new issue Copy permalink