[PDFBOX-216] Sign .NET DLLs for security

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Won't Fix
• Component/s: .NET
• Assignee: Unassigned
• Reporter: Anonymous
• Created: 16/Nov/06 17:31
• Updated: 10/Oct/14 21:50
• Resolved: 10/Oct/14 21:50

Description

[imported from SourceForge]
http://sourceforge.net/tracker/index.php?group_id=78314&atid=552835&aid=1597881
Originally submitted by benlitchfield on 2006-11-16 09:31.

I`m using your tool at work. It is part of a bigger software solution and it works fine!

Now we have a problem concerning your extracttext.exe – it cannot run from a network drive

because of .net security policy. I wrote a tool that allows application to start from network drives, but

only with one preliminary : it must be strong named.

Could you sign your extracttext.exe and the dll`s used by it ?

You really would save me a lot of work, otherwise I have to replace your tool and so on…

[comment on SourceForge]
Originally sent by danielwilson.
Logged In: YES
user_id=1737686
Originator: NO

I have added a -keyfile line in my build.xml:

<echo>Building PDFBox</echo>
<exec executable="${ikvmc}">
<arg value="-reference:${ikvm.dir}/bin/IKVM.GNU.Classpath.dll" />
<arg value="-reference:${ikvm.dir}/bin/IKVM.AWT.WinForms.dll" />
<arg value="-reference:bin/${fontbox.name}.dll" />
<arg value="-reference:bin/${lucene.name}.dll" />
<arg value="-reference:bin/${lucene-demos.name}.dll" />
<arg value="-reference:bin/${bcprov.name}.dll" />
<arg value="-reference:bin/${bcmail.name}.dll" />
<arg value="-target:library" />
<arg value="-compressresources" />
<arg value="-out:bin\${project.name}.dll" />
<arg value="-keyfile:\PerforceCode\StitchViewer\EmsVwrCtl\Viewer.snk" />
<arg value="lib\${project.name}.jar" />
</exec>

Your path & filename will, of course, vary.

The same -keyfile line should work when compiling the executable.

[comment on SourceForge]
Originally sent by benlitchfield.
Logged In: YES
user_id=601708
Originator: YES

Today I found this post; need to try this and verify that this will solve this issue. If anyone could help verify this that would be great.
Ben

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=222499&SiteID=1

Hey all,

I had a problem, where i strong named my project and then i got the error: Cannot emit assembly as referenced assembly is not strong named.

My referenced assembly is created by IKVM tool compiling Java bytecode into .NET MSIL code. I have got one solution to strong name this dll:

1. Create Messages.il using ildasm Messaged.dll /out:Messages.il
2. Use the same key pair (used to strong name the project) to create back the Messages.dll: ilasm Messages.il /dll key="D:\sn.key"

This worked for me, is there any better solution out there that i have missed out.

Also, the relative path isn't working for me.
I am using this: <Assembly: AssemblyKeyFile("D:\sn.key")> instead of

<Assembly: AssemblyKeyFile("..\\..
sn.key")>

Thanks for any help
Vinay Kant

Hi Vinay,

The ildasm / ilasm round trip sounds like your best bet here. The AssemblyKeyFile path should be the relative path from the Visual Studio output location.

-Shawn