phantomtypist

Personally speaking, I'm more on the side of "it's useless" if ~~your~~ the rationale for strong-naming is to prevent tampering/alteration... because of "security". It's been a long time misconception. If...

Here are some thoughts from the .NET core framework team: https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/strong-name-signing.md They themselves even say that strong naming is a vestigial thing from a bygone era of .NET.... however there...

@scottt732 @mmoayyed @serac @TheHokieCoder Your thoughts on the thread and more specifically my last comment with the [proposal](https://github.com/apereo/dotnet-cas-client/issues/68#issuecomment-329591096)?

@TheHokieCoder it's not a lot of effort for me to implement and make the second package. I can see there being a benefit for people that need a strongly named...

Differences between **signing** and **strong naming**: https://blogs.msdn.microsoft.com/shawnfa/2005/12/13/authenticode-and-assemblies/

I'd like to know if anybody that uses this project has a need for an actual signed (using Authenticode) assembly? (i.e. since because this project deals with authentication, it might...

## Strong Naming I believe strong naming really shouldn't be an issue anymore because people making web applications should be deploying the dependencies/references inside the app's bin folder (except for...

No. Let me ping them again.

Me and @mmoayyed settled on me getting my employer (university) to obtain one. We get them free from our InCommon CA. I received it back in December.... will probably have...

@TheHokieCoder if you have any ideas for using the cert in the CI process, not publicly exposed, let me know here or on Gitter or email. Like I said I'm...