The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
At a company I used to work for, they installed one of those a shipping container computer facilities, and had a biometric lock (thumbprint scanner) put on it, even after I warned him that it wouldn't be enough.
I managed to get a copy of my bosses thumb print off his coffee mug, unlocked the door, and called him to come and see.
He wasn't happy. He had a CAC card reader installed that also required a 6-digit pin code. It was much more expensive, but at the same time, much more secure.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
1. Disable the alarm by entering a pin and unsetting the correct zone
2. Present your pass to a reader
3. enter you secret 4 digit pin.
4. do your stuff
5. sign out of the room with your card (if you don't you can't get back in)
6. reset the alarm
then you get to walk away, also someone in a different part of the country is watching you on a CCTV feed to make sure that you dont eat, drink, allow un authorised people in, remove equiptment etc.
Every day, thousands of innocent plants are killed by vegetarians.
Even if you don't go all the way to personal smart cards like the CAC JSOP has the pleasure of dealing with, a digital pad that randomizes where each digit is shown will prevent clean/dirty button attacks.
Which is important because even if order does matter, 4 shiney buttons means 4*3*2 = 24 possible combinations; trivial to brute force.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
I have great pains. Our application consists of a launcher and various dlls.
The launcher looks at the fileserver for newer versions of the dll's and copies them over if required, then the main process is run inside the dll.
It works nicely, or should, and means that users always run the latest version. Win-win. Except.
When we copy over the files to the file server from the build server, one of the dll's is marked as from an 'unknown source' and is blocked. I could go into group policies and disable the blocking but that would be for any other dll/exe that should be blocked.
For now, after each update I have to manually unblock the file. Does anyone have an idea of a better solution?
Seems that comments on articles are not sent to the author anymore automatically. NetZ is still around, be it in a somewhat dormant state, the source code is available on GitHub but no one seems interested in it anymore, what a pity.
I did one simple test with a .NET 4.0 application, and got that working.
I know about ILMerge and Fody Costura, and have put those to good use already, the interesting thing about NetZ however is that it zips and encrypts your application which might offer some level of protection.
I share your pain, I have an installer that 'updates' a certain dll to a version that was released when the earth was hot. The worst thing is that version of the dll doesn't have voodoo for the program to work...