oxen-io/session-ios
1
0
Fork 0
mirror of https://github.com/oxen-io/session-ios.git synced 2023-12-13 21:30:14 +01:00
Code Issues Projects Releases Wiki Activity
session-ios/SignalServiceKit/src/Security/OWSFingerprint.h

51 lines
2 KiB
C
Raw Normal View History

New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
// Created by Michael Kirk on 9/14/16.
// Copyright © 2016 Open Whisper Systems. All rights reserved.
NS_ASSUME_NONNULL_BEGIN
@class UIImage;
@interface OWSFingerprint : NSObject
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
#pragma mark - Initializers
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
- (instancetype)init NS_UNAVAILABLE;
- (instancetype)initWithMyStableId:(NSString *)myStableId
myIdentityKey:(NSData *)myIdentityKeyWithoutKeyType
theirStableId:(NSString *)theirStableId
theirIdentityKey:(NSData *)theirIdentityKeyWithoutKeyType
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
theirName:(NSString *)theirName
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
hashIterations:(uint32_t)hashIterations NS_DESIGNATED_INITIALIZER;
+ (instancetype)fingerprintWithMyStableId:(NSString *)myStableId
myIdentityKey:(NSData *)myIdentityKeyWithoutKeyType
theirStableId:(NSString *)theirStableId
theirIdentityKey:(NSData *)theirIdentityKeyWithoutKeyType
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
theirName:(NSString *)theirName
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
hashIterations:(uint32_t)hashIterations;
+ (instancetype)fingerprintWithMyStableId:(NSString *)myStableId
myIdentityKey:(NSData *)myIdentityKeyWithoutKeyType
theirStableId:(NSString *)theirStableId
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
theirIdentityKey:(NSData *)theirIdentityKeyWithoutKeyType
theirName:(NSString *)theirName;
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
#pragma mark - Properties
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
@property (nonatomic, readonly) NSData *myStableIdData;
@property (nonatomic, readonly) NSData *myIdentityKey;
@property (nonatomic, readonly) NSString *theirStableId;
@property (nonatomic, readonly) NSData *theirStableIdData;
@property (nonatomic, readonly) NSData *theirIdentityKey;
@property (nonatomic, readonly) NSString *displayableText;
Remove phone numbers from scannable QR Code Initially they were there to offer richer error messages when the wrong code was scanned. However, we found that people were posting them publicly, misunderstanding the QR codes to be a kind of personal identifier. For one, this isn't useful because the QR codes, like safety numbers, are unique *per* conversation. So they aren't useful in a generic sense. And secondly this is bad because the QR code contains both parties phone numbers. // FREEBIE
2016-11-12 18:50:06 +01:00
@property (nullable, nonatomic, readonly) UIImage *image;
#pragma mark - Instance Methods
- (BOOL)matchesLogicalFingerprintsData:(NSData *)data error:(NSError **)error;
New fingerprint format In coordination with Desktop and Android, iOS will be using all-numeric fingerprints, aka "Safety Numbers". Furthermore, the concept of verifying one identity and then the other has been removed. Instead we ask users to exchange a single number, or scan a single QR code. These credentials are built by combining the users identities. // FREEBIE
2016-10-01 20:42:39 +02:00
@end
NS_ASSUME_NONNULL_END
Reference in a new issue Copy permalink