Changes between Initial Version and Version 1 of Ticket #106, comment 3
- Timestamp:
- Dec 7, 2015, 5:56:28 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #106, comment 3
initial v1 1 1 Okay, how about 2 * Amend the RFC (or even just the implementations) to support a cert for **.scripts.mit.edu doing what we want? Or add support for an extra something field to say "This wildcard can cover multiple levels", so it remains a cert with subject name *.scripts.mit.edufor backwards-compatibility?2 * Amend the RFC (or even just the implementations) to support a cert for `**.scripts.mit.edu` doing what we want? Or add support for an extra something field to say "This wildcard can cover multiple levels", so it remains a cert with subject name `*.scripts.mit.edu` for backwards-compatibility?