-
Use the Visual Studio 2005 Command Prompt under VS2005 to enter console mode (which automatically sets various environment variables).
Unzip the OpenSSL package and go to the OpenSSL directory.
perl configure vc-win32
Try to run the command in this directory, otherwise the configure file cannot be found, or specify the complete configure file path.
ms\do_ms
Run the ms do ms command in the decompression directory.
After the compilation of nmake -f ms is executed in the openSSL decompression directory, after the compilation is complete. The output file is in the out32dll, including the application executable, lib file, and dll file.
Note: When running the fifth step, the CL compiler complains. The Read of the Crypto des ENC file is the Posix Name for This Item is Deprecated, and it is recommended to use Read.
Hehe, I don't want to change all the read functions in OpenSSL to read. Look at the CL error ** error C2220, so go to MSDN to look:
warning treated as error - no object file generated
wx tells the compiler to treat all warnings as errors. since an error occurred, no object or executable file was generated.
It's because the wx option is set to treat all warnings as errors, so...
So open the file in the ms directory in the openssl directory, remove the wx option of cflag, and save it.
-
After powering on, press F8 to select the [Disable Driver Signature Enforcement] option to enter the system; Open [Group Policyr] in the system, and then open [User Configuration] - [Management Template] - [System]; Ignore the **Signature of Device Drivers) in Driver Installation; Or delete the AMD file in the system drive folder. Here's a closer look:
1. Press the [F8] key many times when booting up, and there is an option of [Disable Driver Signature Force] in the pop-up menu, use the up and down keys to select it, and then press the enter key to confirm, you can enter the system;
2. After entering the system, use the [Win] + [R] key combination to open the [Run] input box, enter [, and click OK;
3. Go to Group Policyr and select [Management Template] in [User Configuration], and then click [System] to open it;
4. In [System], you can find [Driver Installation], then click [**Signature of Device Driver] on the right, select [Ignore] below after opening the page, and click [OK];
5. In addition to ignoring the ** signature, you can also find the AMD file through the path of Windows System32 Drivers after entering the system and delete it.
-
1. After restarting the computer, press F8, then the advanced boot interface appears, select "Disable Driver Signature Force" and press Enter.
2. At this time, it will enter the system, and after waiting to enter the win7 desktop, we can restart it again to use the win7 system normally.
3. Then use PC Manager to detect and update the driver for hardware.
-
Resolved: Windows could not verify the file digital signature and could not boot the system.
Method 1: Press F8 after booting to enter the advanced boot interface, the first try to choose to disable the driver signature force, if you can't get in, choose the safe mode to try, after entering the first uninstall the driver software, such as driving life.
After entering, delete the Windows System32 Divers file from the system disk and restart the computer.
This is the system file of the driver software, and if you want to delete it completely, you need to disable the local driver service in the computer management service.
1. The computer is forced to shut down, and then reboot to see if the computer has an option to "repair the computer", if there is no this, just click on an option to enter, to find the "repair computer", and if you can't find it, solve it with the PE article.
Select "Repair Computer" to start the repair;
The system is repairing itself.
Select Don't send
Select "View System Restore and supported advanced options."
If you have a password set on your computer, you will need to enter the password.
Method 2: Repair the computer command prompt (this can be used to enter safe mode).
Select "Command Prompt" to enter for command deletion.
2. In the "Command Prompt" that opens, enter the command line: del f s q, and press enter, as shown in the following figure:
3. After completing the final interface, we can restart the computer and enter the system. If you boot it again and enter the recovery system or reboot indefinitely, turn it on again, and then quickly press F8 and select "The last correct configuration (advanced)".
-
You can use the U disk PE, delete the prompted sys file after entering the PE and try again.
If you can't enter safe mode, it cannot be fixed under the current system.
So it is impossible to repair the system.
-
# ps -a
# ps -e
Task: View non-root running processes.
ps -u root -u root -n task: View the processes run by user vivek.
# ps -u vivek
Task: top command.
The top command provides a dynamic, real-time view of the system in action. Enter top: in the command prompt line
-
# ps -a
# ps -e
Task: View non-root running processes.
ps -u root -u root -n task: View the process of user vivek as if it were a good one.
# ps -u vivek
Task: top command.
The top command provides a dynamic, real-time view of the system in action. Enter top: in the Command Prompt line for the first key
-
Windows does not detect the validity of a certificate when determining whether it is valid, and even if the certificate is several years past its expiration date, as long as it has not been revoked, Microsoft still considers it valid. However, the x509 verify cert function provided by OpenSSL verifies the validity of the certificate, so you need to comment out the part of the validation expiration date and recompile OpenSSL....
config
Make luckily, you don't need to install any dependencies and compile successfully. Add the root directory generated under the project test, OK, you can use it, and now you can start tossing
Find the x509 verify cert function on line 153 of crypto x509 x509 (** view), the local variable ok cache each step verifies whether it passes, and it calls in turn:
check_issued
check_chain_extensions
check_name_constraints
check_trust
check_revocation
internal_verify
check_policy
ok = check_cert_time(ctx, xs);
if (!ok)
goto end;
Take a look at the check cert time function, confirm that it is to check notbefore and notafter, so comment out the above three lines**, and the expiration date will not be detected when the certificate is verified.
Then it's time to recompile OpenSSL and integrate it into the project
-
To put it simply, there are three steps:
1.Purchase or create your own digitally signed certificate file.
There are tools and software that can make digital signature certificates, such as OpenSSL, but self-signed, on other people's machines, the problem that the signature cannot be verified. Unless someone trusts them, they won't install your certificate.
2.Use the utility software to digitally sign the exe or any other file. It can be a free UI tool, such as:
ksign;It can also be something like signtool (Microsoft's command-line tool); You can also use the operating system's wizards (e.g., the wizard for installing, importing, and digitally signing files on Microsoft Windows). Under Xnix, you can use GNUPG (GPG) to go from certificate to signature, all at once.
3.If you're doing program development, you can use a command-line tool like signtool, write a batch process, and then add it to your project's make process to automatically add signatures.
-
2 ways:
1.Use the Crypto API to check digital signatures.
2.Directly read the additional data at the end of the executable file (the data attached to the file length defined by the header of the executable file, also called overlay), to see if there is a digital signature in it (find the feature code by yourself).
-
first using;
** is something like this:
fileversioninfo info = "c:\windows\");
There is a lot of information in the obtained info. You can judge according to your needs.
-
Read a file to determine if there are specific characters in the file? I don't know if I understand it right.
characters')!=-1
The installation failure report "Failed to verify installation file signature" may be caused by an incorrect system time, a missing root certificate, or other reasons. >>>More