Re: Secure deployment of binary perl modules

One way to handle this is to build on one machine and then use either rdist or rsync to update the others.

-derby

update: I should have said --- use the OS's preferred package mechanism to update the build machine (rpm, pkgadd, cpan, whatever ...) and then use rdist/rsync to update the others.

Comment on Re: Secure deployment of binary perl modules

Replies are listed 'Best First'.
Re^2: Secure deployment of binary perl modules by Argel (Prior) on Mar 21, 2007 at 01:07 UTC
And you you should have replaced rysnc/rdist with something more secure like scp/sftp. Upate: Ooops! I was thinking "rcp" when I read "rsync". I agree that it can be made secure. In fact Using Rsync and SSH disccuses how to use it with SSH. I see from the rdist homepage that it has also come a long way. However as they point out many operating systems ship with a much older, insecure version. So I guess Linux users are more familair with the newer version while those of us used to e.g. Solaris are used to the older version. Looks like it is one of those things that one needs to be careful of recommending given the wide audience. I will point out that it looks like both rsync and rdist make use of SSH for better security. So I think my original comment still has validity.	[reply]
Re^3: Secure deployment of binary perl modules by derby (Abbot) on Mar 21, 2007 at 11:33 UTC
No, I shouldn't have -- rsync and rdist are capable of secure transport. -derby	[reply]