---
title: "Discussion on \"Re-signing a .NET assembly after obfuscation: strong names and Authenticode\" | Hashnode"
description: "Discussion on \"Re-signing a .NET assembly after obfuscation: strong names and Authenticode\". Signing and obfuscation have an ordering problem that bites every team the first time they turn on protection in a release pipeline. Both a strong name and an Authenticode signature are signatures ove"
url: "https://hashnode.com/posts/re-signing-a-net-assembly-after-obfuscation-strong-names-and-authenticode/6af328a331aa73066ff0679d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Re-signing a .NET assembly after obfuscation: strong names and Authenticode](https://delta1labs.hashnode.dev/re-signing-a-net-assembly-after-obfuscation-strong-names-and-authenticode?utm_source=hashnode&utm_medium=feed)

Signing and obfuscation have an ordering problem that bites every team the first time they turn on protection in a release pipeline. Both a strong name and an Authenticode signature are signatures ove

1d ago · 7 min read · delta1labs.hashnode.dev  
Read the article

-   [#nebulanet](https://hashnode.com/tag/nebulanet)
-   [#obfuscation](https://hashnode.com/tag/obfuscation)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#guide](https://hashnode.com/tag/guide)

## Written by

[Zero Heartbeat](https://hashnode.com/@clustron)

@clustron

  
[View profile](https://hashnode.com/@clustron)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.