#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 bananu7):

Maybe the solution is just switching to another hash function

What about that? Doesn't that improve the ''chances'' of the collision not being found even more? It looks like an change that's easy enough. Doesn't moving this ticket to _|_ mean that it's effectively being forgotten? -- Ticket URL: http://ghc.haskell.org/trac/ghc/ticket/7634#comment:6 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler