Hi, I m looking for a technique to prevent binary alteration once distributed in the wild.
I have no clue what i m asking for. I was imagining a solution where a signature is prepended to the binary and checked during the startup sequence. However i do understand (well ... i imagine it) the chicken and egg problem behind this question (no way to sign a binary that will gets its signature inserted right after its signature was computed) Is there anything possible ? Is it something i should be worried of, to start with ? (independently of the interest that altering such binary might raises, i d prefer a strictly technical analysis) thanks for feedbacks. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/194e2e4f-e41b-4c23-b241-f8fe1f5da154%40googlegroups.com.
