Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Mon, 13 Aug 2007 14:57:26 -0400 "Boland, John" <jboland-kYvJ4k0XgburIcfx335RAVaTQe2KTcn/@public.gmane.org> wrote: > but, a corporate security policy is a corporate security policy. > i've decided i don't want to be king canute and command the tide to > stop. I can understand corporate security. While working for HP at Raytheon, I was at Raytheon, Bedford where I had root access to the workstations in the HP group and a couple of servers in the lab. I was sent to Sudbury to write a driver. Generally even employees were not given root access to their workstations. The specific workstation I would be using actually belonged to HP, not Raytheon. However, the IT people refused to give me root access, even through the request was bumped up. After several weeks of this, we decided to move the workstation and the fibrechannel board down to Bedford where I did have root access. Shortly after they sent the stuff down to Bedford, the IT people decided I could have root access, but since I was a contractor, they would have to go to security. Security told them that root access was ok as long as a Raytheon employee sat next to me and watched my keystrokes. BTW: The IT people were knowledgeable about Unix, and were well aware one can't write a device driver without having root access. (Almost true, you can edit the code, but you can't compile it since the code had to reside in a specific directory tree.=20 --=20 Jerry Feldman <gaf-mNDKBlG2WHs at public.gmane.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |