[GHC] #7634: MD5 collision could lead to SafeHaskell violation

[GHC]

#7634: MD5 collision could lead to SafeHaskell violation
-------------------------------------+-------------------------------------
        Reporter:  shachaf           |                   Owner:  ekmett
            Type:  bug               |                  Status:  new
        Priority:  normal            |               Milestone:  ⊥
       Component:  Core Libraries    |                 Version:  7.6.1
      Resolution:                    |                Keywords:
Operating System:  Unknown/Multiple  |            Architecture:
 Type of failure:  Other             |  Unknown/Multiple
      Blocked By:                    |               Test Case:
 Related Tickets:                    |                Blocking:
                                     |  Differential Revisions:
-------------------------------------+-------------------------------------

Comment (by ekmett):

 The move out from 7.12 was more an acknowledgement that the CLC wasn't
 planning on tackling this issue in 7.12. If everything is a priority then
 nothing is a priority, and we have lots of actionable issues with far more
 immediate impact.

 Switching fingerprints to something like SHA-256 could be done. In fact it
 is probably a pretty good idea, despite doubling the size of fingerprints
 and having a measurable performance impact -- if a patch was put forth
 then it would by all means be considered.

--
Ticket URL: <http://ghc.haskell.org/trac/ghc/ticket/7634#comment:7>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler