Closed Bug 1352933 Opened 4 years ago Closed 3 years ago

[FlyWeb] Stable naming implementation

Categories

(Core Graveyard :: DOM: Flyweb, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ron.waisberg, Unassigned)

References

Details

Attachments

(6 files)

561 bytes, application/x-shellscript
Details
2.97 KB, application/javascript
Details
13.51 KB, patch
Details | Diff | Splinter Review
306 bytes, text/plain
Details
294 bytes, application/x-x509-ca-cert
Details
1.66 KB, application/x-x509-ca-cert
Details
Attached file generate_signature.sh
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36

Steps to reproduce:

Bug for tracking implementation of stable naming for FlyWeb services.
Attached file server.js
Comment on attachment 8853852 [details]
generate_signature.sh

Generates RSA-SHA256 signature that is ASN.1 encoded in the format nsDataSignatureVerifier::VerifyData expects it
Comment on attachment 8853853 [details]
server.js

Example service implementing authentication flow
Attachment #8853853 - Attachment description: Example service implementing authentication flow → server.js
Initial implementation of stable naming authentication flow in Gecko.

TODO:
- Refactor and split up AuthenticateService()
- Further testing of error cases
- Sanitize mDisplayName
- Figure out why appending ";flyweb.local" also prepends "www." to the spec
- More flexible signature validation
Attachment #8853854 - Flags: review?(kvijayan)
Attached file package.json
Attached file public_key.der
Attached file private_key.pem
Key pair generated for testing
Component: General → DOM: Flyweb
Comment on attachment 8853852 [details]
generate_signature.sh

Note - nsDataSignatureVerifier::VerifyData expects the signature to be ASN.1 encoded in this format: https://dxr.mozilla.org/mozilla-central/source/security/manager/ssl/nsDataSignatureVerifier.cpp#30

Currently this script only generates and encodes an RSA-SHA256 signature properly. While it can be easily expanded to other algorithms, it's quite limiting to force a custom ASN.1 structure on the end user.
Blocks: flyweb
Comment on attachment 8853854 [details] [diff] [review]
stable_naming.patch

Canceling this as the flyweb code is being removed from trunk.
Attachment #8853854 - Flags: review?(kvijayan)
Priority: -- → P2
Overholt: Patches are up, no reviews. Need to assign someone.
Flags: needinfo?(overholt)
Closing this as we're no longer doing FlyWeb.
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Flags: needinfo?(overholt)
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.