Signal-Android/src/org/thoughtcrime/securesms/service
Sam Lanning 69f180a5ec Fix some potential integer overflows for expiration time
In a number of locations in the code, there were conversions of message
expiration times from seconds to milliseconds, and then assigned to `long`
contexts. However these conversions were being done as integer multiplication
rather than long multiplication, meaning that there was a potential for
overflows.

Specifically, the maximum value that could be represented before overflowing
was (2^31 / 1000 / 60 / 60 / 24) days = 24.8 days (< 1 month). Luckily the
current allowed timeouts are all less than that value, but this fix would
remove the artificial restriction, effectively allowing values of 1000x greater
(68 years), at least for android.

Related #5775
Closes #7338
2018-03-07 09:55:24 -08:00
..
AccountAuthenticatorService.java
AccountVerificationTimeoutException.java
ApplicationMigrationService.java
BootReceiver.java
ContactsSyncAdapterService.java
DirectShareService.java
DirectoryRefreshListener.java
ExpirationListener.java
ExpiringMessageManager.java
GenericForegroundService.java
KeyCachingService.java Migrate to Android fingerprints and auth for Signal screen lock 2018-03-05 16:11:49 -08:00
LocalBackupListener.java Support for full backup/restore to sdcard 2018-03-05 16:11:49 -08:00
MessageRetrievalService.java
MmsListener.java
PanicResponderListener.java
PersistentAlarmManagerListener.java
PersistentConnectionBootListener.java
QuickResponseService.java Fix some potential integer overflows for expiration time 2018-03-07 09:55:24 -08:00
RotateSignedPreKeyListener.java
SmsDeliveryListener.java
SmsListener.java
UpdateApkReadyListener.java
UpdateApkRefreshListener.java
WebRtcCallService.java Support for custom call ringtone selection and per-chat ringtones 2018-03-05 16:11:49 -08:00