Source code

[HyperText]

Will you release the SA-MP's source code?

 

In what language has been written?

[The_Grudge]

Will you release the SA-MP's source code?

 

In what language has been written?

They are programming this software in C.

 

No, they will NOT release the source.

[kyeman]

We're not thinking about open sourcing the mod at the moment. This could make it much easier for people to develop cheats and hacks.

 

I won't say it'll never be open source. If the main developers get bored with maintaining it, or simply don't have enough time, we can look at open sourcing it.

 

edit:

 

And in answer to the second question, SA:MP is coded mostly in C++ with small bits of inline asm. We've actually gone to some trouble converting C code into reusable classes.

Edited July 12, 2005 by kyeman

[HyperText]

We're not thinking about open sourcing the mod at the moment. This could make it much easier for people to develop cheats and hacks.

 

I won't say it'll never be open source. If the main developers get bored with maintaining it, or simply don't have enough time, we can look at open sourcing it.

 

edit:

 

And in answer to the second question, SA:MP is coded mostly in C++ with small bits of inline asm. We've actually gone to some trouble converting C code into reusable classes.

About first part (cheats and hacks) I agree with you. But open source code let users to resolve many bugs, and send them to you. Consequently it permits to programming anti-cheats addons.

[J-Fox.GEMM]

Why not just release parts of ur code if it was written in C++, i will do that with the GEM source too, just the part where the script command will be defined and the Sync sect. also the NewTrainers page but every old Trainer will be detected . To compile the code u will need the rest wich is stored passworded at our page then u have to upload ur files then and if it is ok it will be compiled together with our non Dldable source

[Kryptos]

 

Why not just release parts of ur code if it was written in C++, i will do that with the GEM source too, just the part where the script command will be defined and the Sync sect. also the NewTrainers page but every old Trainer will be detected rampage_ani.gif . To compile the code u will need the rest wich is stored passworded at our page then u have to upload ur files then and if it is ok it will be compiled together with our non Dldable source

 

That sounds like more of a hassle then a luxury. Also, when you release certain pieces of the source code, lets assume it's the network and gameplay segments, and you choose to withhold the anti-cheating segment, just becasue you've done this doesn't mean someone can't go ahead and remove the calls made to the anti-cheat module itself and merely create a spoof check which can then be sent to the server to overcome having to load the anti-cheat module. Now, I'm sure you have some elaborate scheme setup so this can't happen, but remember that you're up against people who have an advantage, being the developer of the software you've drawn the short straw in this big game. That aside, I commend you on your efforts to make your software open source, I believe that the F/OSS community is a great area and allows newcomers and veterans alike to come together and learn in a collaboration of intellectual freedom, I've been an active member in this community for some time.

[syc0]

Open-source is more secure. For every person who exploits a bug, there'll be someone fixing it. That's why IE is more vulnerable than Mozilla. But I'd say it should definitely be kept closed until it reaches a stable release.

[jacob.]

 

Open-source is more secure.

Well, you have to realize the GTA community isn't exactly full of gamehackers/programmers. There's nothing really that the 10-20 people could do to an open-source module that the current team couldn't, is there?

 

If the community was thriving with hundreds of developers, all entirely capable of making useful fixes/additions that the current team either hasn't thought of or doesn't have time for, I'd be all for it. But in my opinion, it'd be more effort then its worth with the small developer community we have now.

Edited July 26, 2005 by jacob.

[Kryptos]

 

Open-source is more secure. For every person who exploits a bug, there'll be someone fixing it. That's why IE is more vulnerable than Mozilla. But I'd say it should definitely be kept closed until it reaches a stable release.

 

No, that's not why IE is more vulnerable then Mozilla. The reasoning behind this is that Mozilla has an immediate exploit fix turn-around basis, one that often annoys many of their distributors since they get it online as soon as possible even if this means some of the distributors aren't completely updated. Microsoft however chooses to launch scheduled fixes on a long-term scale, so if an exploit is discovered in the wild a day after their previous update then the new fix will have to wait until the next update scheduled, which can often be months away. Whether or not the code is open sourced or not doesn't change the fact that it can be reversed, or exploited easier, and using the example of browsers is horrible since part of Internet Explorers code is in fact online in the Windows 2000 Source Code package that was leaked/stolen. The only thing that source code truly aids reversers with is being able to see the flow of everything, any quick hacks that could easily be exploited, or various other pieces of a program that may be harder to notice through a mere code analysis. And since we're talking about exploits, the people who code exploits are fluent in shellcoding, so they essentially already have direct access to the programs source code with the executable alone. This is just to clarify your misconception.

[Sobeit]

Open-source is more secure. For every person who exploits a bug, there'll be someone fixing it. That's why IE is more vulnerable than Mozilla. But I'd say it should definitely be kept closed until it reaches a stable release.

the only reason its more secure is because it is flawed.

 

there are numerous things that could be exploited, and if kept private...never be fixed.

 

(there isnt a myg0t for every community people)

 

exploits dont just magically pop up, people have to discover them then either tell the public or a developer.