keejef
/
session-ios
mirror of https://github.com/oxen-io/session-ios
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
master
dev
voice-calls-2
voice-calls
authentication
2.5.0
2.4.5
2.4.4
2.4.3
2.4.2
2.4.1
2.4.0
2.3.2
2.3.1
2.3.0
2.2.14
2.2.13
2.2.12
2.2.11
2.2.10
2.2.9
2.2.6
2.2.4
2.2.2
2.2.1
2.2.0
2.1.1
2.0.3
2.0.2
2.0.1
2.0.0
1.0.0-alpha.1
audit-2
audit
2.8.0
2.7.4
2.7.3
2.7.2
2.7.1
2.7.0
2.6.3
2.6.2
2.6.1
2.6.0
2.2.8
2.2.7
2.2.5
2.2.3
2.1.0
1.9.7
1.9.6
1.9.5
1.9.4
1.9.3
1.9.1
1.9.0
1.8.3
1.8.2
1.8.1
1.8.0
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.0
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1-beta
1.5.0-beta
1.5.0
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.0-beta
1.4.0
1.3.0-alpha.1
1.3.0
1.2.6
1.2.5
1.2.4
1.2.3
1.2.1
1.2.0-alpha.2
1.2.0-alpha.1
1.2.0
1.13.0
1.12.9
1.12.8
1.12.7
1.12.6
1.12.5
1.12.4
1.12.2
1.12.1
1.11.9
1.11.8
1.11.7
1.11.6
1.11.5
1.11.4
1.11.3
1.11.24
1.11.23
1.11.22
1.11.21
1.11.20
1.11.2
1.11.19
1.11.18
1.11.17
1.11.16
1.11.15
1.11.14
1.11.13
1.11.12
1.11.11
1.11.10
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.1.0-alpha.4
1.1.0-alpha.3
1.1.0-alpha.2
1.1.0-alpha.1
1.1.0
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0-alpha.3
1.0.0-alpha.2
1.0.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'b4c9f3053d'
${ noResults }
session-ios/SignalServiceKit/tests/Security/OWSFingerprintTest.m

81 lines
4.4 KiB
Matlab
Raw Normal View History Unescape Escape

Fixup some SSK tests Still more to do...
7 years ago
//
// Copyright (c) 2018 Open Whisper Systems. All rights reserved.
//
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
9 years ago
#import "OWSFingerprint.h"
Add server certificate methods to UD manager.
7 years ago
#import "SSKBaseTestObjC.h"
Fixup some SSK tests Still more to do...
7 years ago
#import <Curve25519Kit/Curve25519.h>
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
9 years ago
Add server certificate methods to UD manager.
7 years ago
@interface OWSFingerprintTest : SSKBaseTestObjC
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
9 years ago
@end
Get SSK tests building and running.
7 years ago
#pragma mark -
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
9 years ago
@implementation OWSFingerprintTest
- (void)testDisplayableTextInsertsSpaces
{
NSString *aliceStableId = @"+13231111111";
NSData *aliceIdentityKey = [Curve25519 generateKeyPair].publicKey;
NSString *bobStableId = @"+14152222222";
NSData *bobIdentityKey = [Curve25519 generateKeyPair].publicKey;
OWSFingerprint *aliceFingerprint = [OWSFingerprint fingerprintWithMyStableId:aliceStableId
myIdentityKey:aliceIdentityKey
theirStableId:bobStableId
theirIdentityKey:bobIdentityKey
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
9 years ago
theirName:@"Bob"
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
9 years ago
hashIterations:2];
NSString *displayableText = aliceFingerprint.displayableText;
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(0, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(1, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(2, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(3, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(4, 1)]);
XCTAssertEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(5, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(6, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(7, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(8, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(9, 1)]);
XCTAssertNotEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(10, 1)]);
XCTAssertEqualObjects(@" ", [displayableText substringWithRange:NSMakeRange(11, 1)]);
}
- (void)testTextMatchesReciprocally
{
NSString *aliceStableId = @"+13231111111";
NSData *aliceIdentityKey = [Curve25519 generateKeyPair].publicKey;
NSString *bobStableId = @"+14152222222";
NSData *bobIdentityKey = [Curve25519 generateKeyPair].publicKey;
NSString *charlieStableId = @"+14153333333";
NSData *charlieIdentityKey = [Curve25519 generateKeyPair].publicKey;
OWSFingerprint *aliceFingerprint = [OWSFingerprint fingerprintWithMyStableId:aliceStableId
myIdentityKey:aliceIdentityKey
theirStableId:bobStableId
theirIdentityKey:bobIdentityKey
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
9 years ago
theirName:@"Bob"
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
9 years ago
hashIterations:2];
OWSFingerprint *bobFingerprint = [OWSFingerprint fingerprintWithMyStableId:bobStableId
myIdentityKey:bobIdentityKey
theirStableId:aliceStableId
theirIdentityKey:aliceIdentityKey
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
9 years ago
theirName:@"Alice"
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
9 years ago
hashIterations:2];
OWSFingerprint *charlieFingerprint = [OWSFingerprint fingerprintWithMyStableId:charlieStableId
myIdentityKey:charlieIdentityKey
theirStableId:aliceStableId
theirIdentityKey:aliceIdentityKey
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
9 years ago
theirName:@"Alice"
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
9 years ago
hashIterations:2];
XCTAssertEqualObjects(aliceFingerprint.displayableText, bobFingerprint.displayableText);
XCTAssertNotEqualObjects(aliceFingerprint.displayableText, charlieFingerprint.displayableText);
}
@end