Re: [Sidrops] Manifest entry filename validation

[Robert Kisteleki <[e-mail]>]

>> The following restrictions are imposed on the names that appear in the
>> fileList:
>>
>> 1. Only a subset of IA5string characters are permitted: a-z, A-Z, 0-9, . (DOT), - (HYPHEN), and _ (UNDERSCORE).
>>
>> 2. Each name MUST be suffixed with the appropriate filename extension defined for the object type, and the filename extension MUST be lowercase, e.g., '.cer' or '.roa'.
>>
>> 3. The . (DOT) character MUST appear exactly once.
>>
>> As an example, 'vixxBTS_TVXQ-2pmGOT7.cer' is a valid filename.
> 
> 
> Looks good. However, after an internal discussion during which we realised that
> empty names (e.g. .cer) were valid filenames under the previous proposal, and
> after validating that all current valid objects from the major trust anchors
> adhere to our proposal, we would like to propose:
> 
> ----------
> Section 4.2.2 "Names in FileAndHash objects"
> 
> Names that appear in the fileList MUST consist of one or more characters from
> the set a-z, A-Z, 0-9, - (HYPHEN), or _ (UNDERSCORE), followed by a single .
> (DOT), followed by a three-letter extension a-z.
> 
> As an example, 'vixxBTS_TVXQ-2pmGOT7.cer' is a valid filename.

At this point perhaps a regexp would be simpler to specify?

I also note that both miss a clause saying the filenames are case 
sensitive, thus 'vixxBTS_TVXQ-2pmGOT7.cer' and 
'VixxBTS_TVXQ-2pmGOT7.cer' are different certificates.

Robert