Export Control Classification Number (ECCN) for Castle Windsor

48 views

Skip to first unread message

Patryk Woźniak

unread,

Mar 26, 2015, 7:51:31 AM3/26/15

to castle-pro...@googlegroups.com

We use Castle Windsor in our software and now our legal department asked about two strange things:

1) We want to sell our software in US. Whether the Castle Windsor has ECCN (Export Control Classification Number) or not?

2) Whether the Castle Windsor use any encryption functionality or not? We looked into the code of those libraries and they don't seem to even reference any encryption related namespaces. But we are not familiar with the whole architecture of .NET so we are not 100% sure where all "encryption" related code is located. But we don't think it is the responsibility of IoC Container to encrypt anything.

Can anyone answer these two questions?

Jonathon Rossi

unread,

Mar 26, 2015, 8:03:08 AM3/26/15

to Castle Project Development

I'll preface my comments with the usual I'm not a lawyer and my comments are just my opinion, they are provided as-is with no warranty...

1. None of the Castle Project libraries have a ECCN. Looking this thing up it seems Microsoft provides details for the .NET Framework, http://www.microsoft.com/en-us/exporting/eccn.aspx.

2. Castle Windsor's WCF facility has X509 certificate functionality used via the .NET Framework, however I don't recall there being any encryption functionality anywhere in the Castle libraries that isn't using the .NET BCL.

Hope that helps you comply with your lawyer's demands :)

--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to castle-project-d...@googlegroups.com.
To post to this group, send email to castle-pro...@googlegroups.com.
Visit this group at http://groups.google.com/group/castle-project-devel.
For more options, visit https://groups.google.com/d/optout.