ENGINE-429 pEp to pEp always encrypts subject
authorDirk Zimmermann <dirk@pep-project.org>
Thu, 26 Apr 2018 09:37:05 +0200
changeset 6029a560dd0fd0c
parent 601 10ac2d9704ac
child 603 9b4e42283f66
child 604 1af0cfd35a84
ENGINE-429 pEp to pEp always encrypts subject
pEpObjCTests/PEPSessionTest.m
     1.1 --- a/pEpObjCTests/PEPSessionTest.m	Thu Apr 26 08:00:22 2018 +0200
     1.2 +++ b/pEpObjCTests/PEPSessionTest.m	Thu Apr 26 09:37:05 2018 +0200
     1.3 @@ -1178,7 +1178,7 @@
     1.4      XCTAssertEqualObjects(encMessage.shortMessage, @"p≡p", @"Subject should be encrypted");
     1.5  }
     1.6  
     1.7 -- (void)testConfigUnencryptedSubject_encryptedSubjectDisabled
     1.8 +- (void)testConfigUnencryptedSubjectEncryptedSubjectDisabled
     1.9  {
    1.10      // Setup Config to not encrypt subject
    1.11      [PEPObjCAdapter setUnEncryptedSubjectEnabled:YES];
    1.12 @@ -1186,8 +1186,8 @@
    1.13      // Write mail to yourself ...
    1.14      PEPMessage *encMessage = [self mailWrittenToMySelf];
    1.15  
    1.16 -    // ... and assert the subject is not encrypted
    1.17 -    XCTAssertNotEqualObjects(encMessage.shortMessage, @"p≡p", @"Subject should not be encrypted");
    1.18 +    // pEp to pEp uses message 2.0, which always encrypts subjects (ENGINE-429)
    1.19 +    XCTAssertEqualObjects(encMessage.shortMessage, @"p≡p", @"Subject should be encrypted");
    1.20  }
    1.21  
    1.22  #pragma mark - Helpers