Workplace Policies
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
we fire people who think of that.
I'd rather be phishing!
-
we fire people who think of that.
I'd rather be phishing!
I would fire anyone that installs Symantec Antiproductivity.
Wrong is evil and must be defeated. - Jeff Ello
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
Toto1107 wrote:
and have the source code to review to make sure we are not writing malware
..you found someone who is more paranoid than I am. That is saying a lot :) Simple advice; run and don't look back. A company that is crippling itself will not survive long. --edit Forgot to answer what the 'workplace' does. Well, we are local admins, install all kind of crap, and getting a code-review, well, I would be delighted. If I would install Warcraft, then I guess I would be fired, which sounds reasonable to me.
Toto1107 wrote:
So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware
Sorry, everytime I read it start to laugh, it simply feels like a joke. Are you allowed to use the toilet without supervision? Is there someone next to you when you are "reading" in that spot, just to make sure that you are not building malware on your smartphone to take over and destroy the company? You should tell your boss that, since you work with code, there's a security risk that you steal that code. You should not have access to the code, and write it on paper, based on the specifications that you are not allowed to see. Then someone with the correct access-permission can type it in, build it, and hand you any build-errors back on paper :thumbsup:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^][](X-Clacks-Overhead: GNU Terry Pratchett)
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
We stopped working with Symantec products for a long time now. I remember a huge problem with BackupExec, I think it was back in 2010, and it took three weeks to get a support from an engineer who did not even manage to figure out the cause of the issue. And when a friend or someone of my family buys a new laptop, and I take care of the initial configuration, Symantec is on my blacklist.
while (true) {
continue;
} -
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
Handle it by finding a new job. If they can't trust the coders, who can they trust.
If it's not broken, fix it until it is
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107
Fortunately (for me ;) ) my last adventure with Symantec was about 10 years ago when it was common for it to lock and scan files frequently... for example during compilation resulting in constant failing builds. Fortunately we get permission back then to exclude source folders from "protection" :) Looking at your story nothing really changed in their "development friendly" practices.
-- "My software never has bugs. It just develops random features."
-
we fire people who think of that.
I'd rather be phishing!
That's a bit harsh. Your typical non-technical PHB doesn't have the background to realize what a disaster it would be; any punishment beyond smirks and poorly suppressed laughter from the CTI/CIO when he suggests it the boardroom is overkill. Now if it's **IMPLEMENTED** that's a different story; then burn management to the ground.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging 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? --Zachris Topelius 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
-
Along the same lines as Windows Admin Rights for Software Engineers.... Our workplace recently decided to push down a policy for Symantec to scan for Reputation risks - any software not defined by Symantec's large community of users is marked as a WS.Reputation.1 risk and will be deleted. Add to that if found multiple times you get automatically disconnected from the workplace network. We write software for our INTERNAL use only, for testing our products. It is not "sold" to the general public. So IT wants to know the EXACT spelling, the EXACT paths, and have the source code to review to make sure we are not writing malware instead of our jobs. A few of us got banned and it took 8 business days to get computer access back to "normal". In the mean time I got to organize my file cabinets ... They put the "delete" and ban on hold for now while they try and figure out how to make it work... For now I rename my executables to OUTLOOK.exe, POWERPNT.exe :-\ So how does your workplace handle this ?
Toto1107