Re: Re2: The quest for pure perl

Your probably right.

I keep thinking to myself that given the right set of limited permissions for a specifically set up userid with no read/write/execute access outside a download/build directory created specifically for each given download and destroyed immediately after the PPM is built, it ought not be a security risk. That said, the only time I set up anything similar (under NT, I wouldn't have a clue under *nix) the aim was prevention of accidents rather protection from deliberate attack.

Oh well. Another transient thought bites the dust:)

Examine what is said, not who speaks.

The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.

Comment on Re: Re2: The quest for pure perl

Replies are listed 'Best First'.
Re: Re: Re2: The quest for pure perl by hackdaddy (Hermit) on Feb 19, 2003 at 23:50 UTC
I am not sure how to do this with Unix, but with Windows using Ghost we could the automate the installation of a fresh OS image and perform an installation (or, whatever operation). We had just about every MS OS flavor. When we were done, we would install another fresh OS image and start another test. It seems like it would be possible to isolate a build machine that used a fresh OS image for each build. I am not sure about the implications for doing this in the Unix world.	[reply]
Re: Re: Re: Re2: The quest for pure perl by BrowserUk (Patriarch) on Feb 20, 2003 at 03:44 UTC
Agreed. We used Ghost'd test images too. We also used Terminal Server to present Ghosted partitions where customers could be provided with a test environment and if they screwed stuf up, it took around 10 mins to restore the image partition and they could start again. That was a different time and place though. Examine what is said, not who speaks. The 7th Rule of perl club is -- pearl clubs are easily damaged. Use a diamond club instead.	[reply]