China DOS Union

Originally posted by ZJHJ at 2008-4-29 09:24 PM:
There is a problem that I don't understand. Although it has become an exe in this way, I can also specify the release path, and what is released is the original code. The exe has been encrypted, but when you RAR package and view it, the original form is still exposed.
Using QuickBFC.EXE to RAR...

RAR package and view? Since you have encrypted it, how can you view it without a password?

Most of the so-called software that compiles into exe now has to release the source code first and then run it. I have seen ones made with assembly, which do not support Chinese, and the code will also make mistakes if there are special characters.

I feel that there can't be a real so-called "compile" bat to exe software. After all, bat is interpreted and executed...

Now I will upload another one made with assembly that compiles the bat file into an executable com file. You can change the com suffix to exe.

Download: On the first floor

"After encryption, the first time can only be brute-force cracking. No one can find the source code in the temporary path."

Can this be explained? I encrypted it, but after running, I can still find the source code in the temp directory.

"No one can find the source code in the temporary path"???

What does this refer to?

Hehe, I just found out this trick. If the LZ didn't say it, I think I still wouldn't know. Thanks for sharing.

Also, how to use the tool uploaded by the LZ? I downloaded it, but can't convert it.

[ Last edited by jonsonqf on 2008-4-30 at 01:11 AM ]

Originally posted by jonsonqf at 2008-4-30 01:08 AM:
"This is the first time after encryption, only brute force can be used. No one can find the source code in the temporary path"

Can this be explained? I encrypted it, but after running, I can still find it in the temp directory...

Regardless of whether the RAR self-extractor is encrypted or not, after running, it will generate the decompressed file in the temp directory and execute it. This is its working mechanism. The owner's meaning is that before decompression, without knowing the password, it is impossible to obtain the source code. Only by obtaining the password can one have the right to view the source code, etc.

Originally posted by evezero it prompts that it's a wrong account or the password is incorrect, it will prompt that it can't log in. The system said that it's a wrong account or the password is incorrect, it will prompt that it can't log in.

Wait for your reply!

By the way, I don't know if you have used the "bat2exec, which compiles bat into a com executable file" that I downloaded and executed but couldn't convert it.

Bump it, this encryption method is somewhat okay to a certain extent

I mean, you've already used RAR to generate an EXE for others to run. There's no issue with passwords. If you then package the EXE into a RAR again, see if it's the source code? It's just that the extraction path is up to you. It doesn't really play much of an encryption role, it's similar to writing to a Notepad with Unicode encoding.

-

WinRAR self-extracting command, give an example!

-

Originally posted by ZJHJ at 2008-5-1 09:37 PM:
I mean, you've already generated an EXE using RAR, which is for others to run. There's no issue with passwords here. If you then package the EXE into a RAR, check if it's the source code? It's just that the extraction path is determined by you. It doesn't provide much encryption at all,
similar to writing to a Notepad with Unicode encoding.

In my opinion, except for the real method of compiling a BAT into an EXE file (for example: the method of compiling a BAT into a COM executable file like the one on the first floor, but this small tool is not universal), other methods don't have absolute encryption. The purpose of me posting this thread is to tell
those newbies who are still using quickbfc to convert BATs. Since it's not really compiling into an EXE, the ready-made RAR is much more convenient than quickbfc. Doesn't the self-extracting one also support commands?

Originally posted by plp626 at 2008-5-4 07:39 PM:


In my opinion, except for the method of truly compiling bat into an exe file (for example: the one in the first floor that compiles bat into a com executable file, but this small tool is not universal), there is no absolute encryption in other methods ...

The building owner is right........

It is a method. And it is an absolute method.....

Actually, the encryption of bat is really quite fragile...

The original intention of .bat was simply to improve the efficiency of transaction processing. Why do you have to encrypt with .bat? Do you have to use a broadsword and spear to fight against Japanese invaders carrying missiles?

Hehe, I didn't know before````Now I know!