Developer forums (C::B DEVELOPMENT STRICTLY!) > Contributions to C::B
Linux beta testers wanted
takeshimiya:
I opted-in the other day for the compile farm, but I dunno how to SSH correctly (I'm newbie here, when I try to login it says wrong password).
I'm also not sure if you need to figure as a project developer.
mandrav:
--- Quote from: Takeshi Miya on November 22, 2005, 10:34:26 pm ---I'm also not sure if you need to figure as a project developer.
--- End quote ---
That's true, only project developers can opt-in for compile farm usage (at least that's what I read :P).
thomas:
I am against using the compile farm because of the implied security risks.
Of course nothing can prevent any of the Code::Blocks developers to deliberately build some kind of malware into the executable, but hey! I guess we should have that much trust!
On the other hand, you have absolutely no clue what goes on when you use a computer at the SF compile farm. You did not install the machine, you don't own it, and you don't know who has been using it before.
It might be just fine, but you might as well unintentionally bundle a trojan with your executable -- and unless it is a well-known variant, it may as well go unnoticed.
This possiblity is quite an argument against using the compile farm.
SF recommends against it, too:
--- Quote ---While we encourage the use of the Compile Farm for porting your software to new platforms, and for testing your software, we discourage the use of the Compile Farm for creating packages for distribution to other users.
--- End quote ---
sethjackson:
--- Quote from: thomas on November 22, 2005, 11:20:56 pm ---I am against using the compile farm because of the implied security risks.
Of course nothing can prevent any of the Code::Blocks developers to deliberately build some kind of malware into the executable, but hey! I guess we should have that much trust!
On the other hand, you have absolutely no clue what goes on when you use a computer at the SF compile farm. You did not install the machine, you don't own it, and you don't know who has been using it before.
It might be just fine, but you might as well unintentionally bundle a trojan with your executable -- and unless it is a well-known variant, it may as well go unnoticed.
This possiblity is quite an argument against using the compile farm.
SF recommends against it, too:
--- Quote ---While we encourage the use of the Compile Farm for porting your software to new platforms, and for testing your software, we discourage the use of the Compile Farm for creating packages for distribution to other users.
--- End quote ---
--- End quote ---
Maybe use it for testing... Then compile the released version on a dev's PC??
takeshimiya:
thomas: Compile Farm is for testing, for the packages we'll have C::B in official repositories I hope.
BTW, I highly doubt security risks, they are *nix machines and they'd give you a limited account, and users of the Compiler Farm can't install software system-wide.
Trojans in linux? And Sourceforge? Even Compile Farm, which is disabled by default in all accounts? I agree to not make packages from these boxes, but you got a little paranoid, ne? :P
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version