Re: A little off topic, but ...
From: Nick Malik (nickmalik_at_hotmail.nospam.com)
Date: 10/08/04
- Next message: Eric Sabine: "Joining threads; why?"
- Previous message: Tim Gallivan: "Re: A little off topic, but ..."
- In reply to: Tim Gallivan: "A little off topic, but ..."
- Next in thread: James Curran: "Re: A little off topic, but ..."
- Reply: James Curran: "Re: A little off topic, but ..."
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 08 Oct 2004 15:04:14 GMT
First off, there is no reason why the development network shouldn't connect
to the web.
It doesn't have to connect to the main network in order to connect to the
web.
Secondly, if you are using a Microsoft network (and I assume you are,
considering that you posted here :-),
then suggest to IT that they can set up the dev network so that the main
network does not trust it.
Then, code developed on the dev network cannot access resources on the main
network.
A firewall can prevent most TCP ports from passing through. Nice thing
about a firewall: you can set it up so that connections that originate in
the main network can get a response from the dev network. You can then use
terminal server from your desktop to drive the server, install software, do
other work...while the dev server cannot host code that can access the main
network. Firewalls are not very expensive, either.
The "Network Security stick" has swung too far in your organization, my
friend. There are better ways to secure the network than to simply assume
that developers cannot be trusted.
--- Nick
"Tim Gallivan" <nospampleasetim.gallivan@edu.gov.on.ca> wrote in message
news:OrGD3ITrEHA.4004@TK2MSFTNGP10.phx.gbl...
> I'm a developer for a government ministry (I'll let you guys figure out
the
> rest). The IT "powers-that-be" have stipulated that all software
development
> be performed on a separate network that in no way connects to the "main"
> network - ever. IT's blanket reason is "network security". These separate
> networks cost a lot of money - a second database server, app server and a
> couple of development machines, they are unpatchable (can't connect to the
> web to get updates), you've got to burn a cd everytime you bring out a new
> version, and burn a DVD to move big database updates back and forth. OK,
> enough griping!
>
> Would any of you be able to point me at some resources dealing with
software
> development strategies, or even personal examples of how they do it where
> you work? I need to come up with a strategy for my department.
>
> Thanks in advance,
> Tim Gallivan
> I know I'm a great teacher because when I give a lesson, the person never
> comes back.
>
>
- Next message: Eric Sabine: "Joining threads; why?"
- Previous message: Tim Gallivan: "Re: A little off topic, but ..."
- In reply to: Tim Gallivan: "A little off topic, but ..."
- Next in thread: James Curran: "Re: A little off topic, but ..."
- Reply: James Curran: "Re: A little off topic, but ..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
