/λ/ - programming

If you want to help people with it, why not just leak it all?

if you wish to remain anonymous, only leak things that are easily accessible from within the organization, nothing that is only specifically accessible to one group. of course, small organizations probably have small security, but better to not single yourself out.

also, do not from your computer, or your user account access things that you have no reason to look at. take things covertly, download things you are already looking at, don't make a loud noise when you release them.

Additionally, I echo our other alice: the most useful files arent going to be those that make reverse engineering possible; the most useful are going to be the plain source files, or litterally whatever you can reach.

your materials are far more likely to be used if they are easier to use. reverse engineering takes a great deal more effort than simply reading and reworking code.

>>936
The code is mostly useless for re-implementation, it cannot be reused or even read due to legal issues. See for example: https://www.reactos.org/reset-reboot-restart-legal-issues-and-long-road-03
I don't know if it applies to leaked documentation too or not.

Of course if it's a malware or something releasing the source code can be useful in combating it. (And making thousands of copycat malwares, it's illegal anyway.)

But keep in mind OP that leaking is illegal and can get in trouble both you and the persons getting into contact with the leaked stuff.

>>933
So let me get this straight: you're working at a small software company who's probably only working or at least focusing on this one project, a project that could really help people, and you're going to repay them for their brilliance by bankrupting them. Whoop-dee-doo. What a great idea.

>>939
The leak won't bankrupt them. No professional company is interested in getting sued and a leak of the source does not remove patent protection.

>>940
If people can get the program for free, why would they buy it?

>>933
dood don't leak, it's not worth it because of legal repercussions unless you're looking forward to having your horizons and anus expanded in jail or something

if the software actually is useful start a free software clone under pseudonym, gather people that would benefit from the project to help you. you can cheat and look at original closed source program to help you get the design right or to get unstuck with eventual hard problems. your employer won't try legal actions as long as they don't suspect the project owner is one of their employees, and you only risk breaching employment contract by working on competitor product rather than outright leaking trade secrets
also the free software version would have the potential to eventually become better than the original, and having a free version available is way better than a leaked proprietary one.

>>939
They wrote that it could help people if it was open source.

Whatever it is, if you saiy if it were open source,it would help people, you should definitely leak it. Even if distributing it would be impossible within large corporations, things like AUR and hidden service repositories will always keep a copy, plus there's bittorrent.

op again.

i could try to get the source from build server. just found a little hole in security.

the next step: to whom i could leak it? do you know any engineering/tech collectives?

>>945
Wookieleaks and all imageboards you can think of.