oxen-io
/
session-ios
mirror of https://github.com/oxen-io/session-ios.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
session-ios/SignalServiceKit/protobuf/Fingerprint.proto

25 lines
656 B
Protocol Buffer
Raw Normal View History

Swift protos for Envelope
2018-06-07 07:57:59 +02:00
// iOS - since we use a modern proto-compiler, we must specify
// the legacy proto format.
syntax = "proto2";
CR: tweak proto class name, include yet-to-be-used protos // FREEBIE
2018-07-25 21:46:49 +02:00
// iOS - package name determines class prefix
package FingerprintProtos;
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
option java_package = "org.whispersystems.libsignal.fingerprint";
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
option java_outer_classname = "FingerprintProtos";
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
message LogicalFingerprint {
Respond to CR.
2018-08-03 20:03:02 +02:00
// @required
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
optional bytes identityData = 1;
// optional bytes identifier = 2;
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
message LogicalFingerprints {
Respond to CR.
2018-08-03 20:03:02 +02:00
// @required
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
optional uint32 version = 1;
Respond to CR.
2018-08-03 20:03:02 +02:00
// @required
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
optional LogicalFingerprint localFingerprint = 2;
Respond to CR.
2018-08-03 20:03:02 +02:00
// @required
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
optional LogicalFingerprint remoteFingerprint = 3;
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
}