Hello Forum Members, I know it may sound silly but we all know that reverse engineering of the TCP is done very easily. I too had a case where one of a partner in Mumbai had crack one of my TCP and using it for his own good. You can watch the video of that partner here [Watch Video #1] which was originally made by me and had published it here [Watch Video #2]. We have filed a complain for so in TSPL but they didn't respond well so i was thing more ways to securing it externally with whoso ever needed like binding it with DLL or any other exe which will verify it and the allow the user to use it. I really tried hard thinking about the same but did not found any solution for the same so lets us all think on some solution to secure the tcp so that our precious work won't get cracked by some other user and use it for his free will. Video #1 See my comment on the above video. Video #2 This video was very old one and we have made much changes on our tcp too and he got our latest tcp but do note the dll output which was same as well he has skiped a part where our name was getting displayed. He can do reverse engg on tcp but could not do on the dll so he skip that part. Thanks & Regards Manthan Patel.
Please note my points / observations as under: a. Unless TCP is compiled in "irreversible mode" it cannot be decompiled by anyone, including TSPL. b. Even in case, let's assume anyone can hack it (highly improbable), there will be very few programmers who can hack it and that too not full code. c. Your program is innovative and useful, but not yet a major or big program, that anyone will spend lots of time and efforts to hack it. d. TSPL will not respond, because it is not their domain, but internally they might be tightening any loopholes in security, if any. e. More likely, either your computer is compromised or your cloud storage is hacked where you might be having backup stored, OR someone is leaking the information. I have had similar experience like yours earlier, but it was more due to lackadaisical security on my part, rather than the robustness of the compiled TCP. However, after installing a commercial firewall as well as certain measures like stop taking on screens (Teamviewer/Anydesk).... I have kept my core system (where i stored the raw TXT files and project files) free of any kind of outside interference.
Hello @Amit Kamdar , Thank you for looking on my post and replying it. I understood all your above point & will also consider same for my future phases. Still is there any binding mechanism we can use in the system so that a tcp can work only on that particular machine? I can write code on DLL side to verify the machine but if my tcp is likely to get hack or reversed the all he can do is comment that code n move on so protecting from DLL will means nothing to it. Some suggestion on this will be a great help. Regards, Manthan Patel
I presume, you have a licensed Tally Developer......if yes.... then you can bind the TCP to work with the specified Serial Numbers only. In a licensed Developer you can go to "Active Project Properties"...select the TAB ... "Build options".....and within that.... check the box "Irreversible" and also check the box "Authorization required" and specify the serial number(s) against which you want the TCP to be compiled.
please make a small inconsequential TDL (a small TDL for "hello there") ..... then you compile it into a TCP and then send it to me on email, so I can check, if there are any control measures you can take or not. nehalsofttech@gmail.com
Hello, Yes, we are compiling tcp in the format you specified. For testing i've attched 4 tcp in the attachment complied in all specific format (check the tcp's name). Even i am trying to decompile all the four tcp's from tally solutions portal. Lets see which of them get de compiled and which on them survive. Kind Regards, Manthan Patel
Good... am not able to open any..... However, the regular ones, you would be able to open on the TSPL website (your account).
Yeah, i have been able to decompile regular one using my login on tallysolutions webiste but was not able to decompile any of the irregular one. So may be there must be someone who is leaking the information outside. I will try to protect our code by the way you mentioned it above and will try to find an enhance solution on tcp with machine binding protocol so it might be useful for machine specific policy. Regards, Manthan Patel.
Kindly take windows protection......a) ensure ur windows login has a password and b) ensure, if you save data on the CLOUD, then password is strong. I do not think that TCP is very easily hacakble. 1) requires lots of computing power 2) people won't try to hack unless it is a big and a decisive program. So yes, all signs points inwards....
Thanks @Amit Kamdar, we will try to find & fix our security loops so that this things won't happen again.
Respected sir, I appreciate your work but still I would like to let you know that decompiling a program is quite easy and I guess TSPL is not interested to make it more secure.
