.net - Is it absolutely necessary to any internal app must be signed? -
I have written a WPF app, which has been used by us for almost a year today to make changes to the app Is needed, and it needs to be republished on our network drive, where it will be picked up by our users. However, I could not publish it because I was getting an error message that this certificate was over. I forgot, but a year ago I would have generated a test certificate which I had linked to the app when I published it initially.
Fast forward for today, as I said, I made some changes and tried to publish it again, when I came to know that the problem We do not have to sign the assembly of this app - it is only used internally and will never be used outside of our agency. I went to the properties of the project, opened the signing tab, and decided to clear the checkbox next to "Click Signon Manifest Sign In" on a command. I made it again, published it again (there was no error in this matter) and it was checked to check on the machine whether I can install it, it is okay, and works.
So, the bottom line is this; Is it absolutely necessary that any and all click-on applications should be signed forever and forever? In our case, writing for my agency only, an app that will only be used here, I just do not see the need.
No, not really. Users "this app is not signed and your money, your family and your favorite jumper" can quickly steal, but in an internal app it can argue that this is not a problem This is because it is from a known source and you can publish the instructions. For apps that you were building for external use (or more accurately for your customers), it's not really that good that those users get something like this, So you want to get the appropriate certificate from the reliable authority.
Comments
Post a Comment