James, in the case of most open source projects this goal is fruitless because the private strong name key is available in source control.
On Thu, Feb 11, 2010 at 7:08 PM, James Curran <[email protected]>wrote: > On Thu, Feb 11, 2010 at 3:48 AM, Jonathon Rossi <[email protected]> > wrote: > > I guess might is the keyword here, whereas everyone above said the GAC is > > evil so they don't need strong named assemblies in their applications. > > But strong-naming isn't just about using the GAC -- It's mostly about > having a verifiable origin. In a world where corporate IT departments > lock out all kinds of software coming from the Internet, being able to > show that an assembly is the original version and not one create by a > hacker who download and modified the source code is important. > > > Truth, > James > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Development List" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-devel%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-devel?hl=en. > > -- Jono -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
