#12129 NORM Not Tri: Strange filenames used in XO-4 secure boot path

[Zarro Boogs per Child]

#12129: Strange filenames used in XO-4 secure boot path
-------------------------------------------+--------------------------------
           Reporter:  dsd                  |       Owner:  wmb at firmworks.com
               Type:  defect               |      Status:  new              
           Priority:  normal               |   Milestone:  Not Triaged      
          Component:  ofw - open firmware  |     Version:  not specified    
         Resolution:                       |    Keywords:                   
        Next_action:  never set            |    Verified:  0                
Deployment_affected:                       |   Blockedby:                   
           Blocking:                       |  
-------------------------------------------+--------------------------------

Comment(by wmb at firmworks.com):

 The "repeating 4's" problem has already been fixed - by svn 3315 on 9/18.

 On the "how should it work" front, this is the sort of issue that I
 personally find so irritating - and that is the nice way of putting it -
 that I just can't deal with it.  No matter what you do, someone will want
 it to work the other way.  So what I propose is that you or some
 collection of people decide what should happen in every case, write it
 down in the form of a Wiki page with full rationale, and then when people
 later complain, we can point them to that page and the bugs they file will
 be reassigned to you.

 Making it work differently for different types of files is do-able, but
 will be a pain in the ass to code and thus will probably be broken for
 awhile.  This whole security jumble is already a pain in the ass because
 there are so many cases to consider.

 Sorry to be snippy, but like I said, I really really really hate this kind
 of never-ending tweak-a-thon.

-- 
Ticket URL: <http://dev.laptop.org/ticket/12129#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system