请问怎么取消"数字签名"对话框.

[rockally]

我想实现驱动程序的自动安装,所以将响应的文件拷贝到目录中,可是我不知道把.CAT数字签名文件放置到系统盘的什么位置,所以老弹出没有数字签名对话框,请问.CAT文件放置什么位置呢,或者怎么在程序中取消数字签名验证,强制安装驱动呢?谢谢!

[JOSENHUANG]

只有你自己建立一个class，不要安装到系统已经有的class下面，好像就不会提示了

[rockally]

请说明白点,自己建立?

[bager]

安装之前，先修改系统的安全设置，
将“未签名驱动程序的安装操作”设置为默认安装。
安装完成后，再恢复系统的安全设置。

此过程可编程实现（调用secedit.exe的导入导出功能）

[rockally]

我就是需要编程实现,请问怎么调用secedit.exe的导入导出功能?

[oyljerry]

使用 secedit.exe 命令行工具

1.
打开命令提示符（例如，单击“开始”，然后单击“运行”，键入 cmd.exe 并按 Enter 键）。

2.
要应用模板 W2KHG_baseline.inf，您可以使用下面的命令：

secedit /configure /DB W2KHG_baseline.sdb /CFG W2KHG_baseline.inf /overwrite
/LOG HGW2K_baseline.log



有关如何使用 secedit 命令行工具的更完整信息，请在命令行键入 secedit /?。

[bager]

-〉我就是需要编程实现,请问怎么调用secedit.exe的导入导出功能?

1、首先导出一个[“未签名驱动程序的安装操作”设置为默认安装]的配置文件。
2、创建调用secedit的进程，传入相应参数，保存当前安全设置至某临时文件。
3、创建调用secedit的进程，传入相应参数，配合步骤1中创建的文件，导入修改后的安全设置。
4、创建调用secedit的进程，传入相应参数，配合步骤2中生成的临时文件，恢复安全设置。
5、删除临时文件。

在步骤2与步骤4之间可以加入你的驱动程序的自动安装处理

稍微复杂了点，但绝对能满足你的需求。

[lonelyeagle]

数字签名可以将HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\no Driver Signing
中的值改变后取消。值可以取0 1 2

[flyelf]

注册表的修改在xp下没有作用，因此xp下的数字签名想要取消，就用oyljerry(【勇敢的心】→ ㊣X-Monsieur㊣) 和bager(柏哥) 说的方法了
还有的方法就是启动监控线程来监控数字签名对话框

[rockally]

注册表该怎么操作，即怎么将HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\no Driver Signing中的值改变为0，谢谢！

[afc]

已经有CAT文件了就不用改数字签名设置了，用SetupCopyOEMInf
Platform SDK: Setup API
SetupCopyOEMInf

The SetupCopyOEMInf function copies a specified INF file to the %windir%/Inf directory.

A caller of this function is required have administrative privileges, otherwise the function fails.

BOOL WINAPI SetupCopyOEMInf(
PCTSTR SourceInfFileName,
PCTSTR OEMSourceMediaLocation,
DWORD OEMSourceMediaType,
DWORD CopyStyle,
PTSTR DestinationInfFileName,
DWORD DestinationInfFileNameSize,
PDWORD RequiredSize,
PTSTR DestinationInfFileNameComponent
);

Parameters

SourceInfFileName
[in] Full path to the source INF file. You should use a null-terminated string. This path should not exceed MAX_PATH in size, including the terminating NULL.
OEMSourceMediaLocation
[in] Source location information to be stored in the precompiled INF (.pnf). This location information is specific to the source media type specified. You should use a null-terminated string. This path should not exceed MAX_PATH in size, including the terminating NULL.
OEMSourceMediaType
[in] Source media type referenced by the location information. This parameter may be one of the following values.
Value Meaning
SPOST_NONE No source media information is stored in the PNF file. The value of OEMSourceMediaLocation is ignored in this case.
SPOST_PATH OEMSourceMediaLocation contains a path to the source media. For example, if the media is on a floppy, this path might be "A:\". If OEMSourceMediaLocation is NULL, the path is assumed to be the path where the INF is located. If the INF has a corresponding PNF in that location, the PNF file's source media information will be transferred to the destination PNF file.
SPOST_URL OEMSourceMediaLocation contains a universal resource locator (URL) specifying the Internet location from where the INF/driver files were retrieved. If OEMSourceMediaLocation is NULL, it is assumed that the default Code Download Manager location was used.
CopyStyle
[in] Specifies how the INF file is copied into the INF directory. The following flags can be combined.
Value Meaning
SP_COPY_DELETESOURCE Delete source file on successful copy.
SP_COPY_REPLACEONLY Copy only if this file already exists in the INF directory. This flag could be used to update the source location information for an existing INF.
SP_COPY_NOOVERWRITE Copy only if the specified files don't currently exist in the INF directory. If the INF does currently exist, this API will fail and GetLastError returns ERROR_FILE_EXISTS. In this case, the existing INF file's filename will be placed into the appropriate field in the destination INF file's information output buffers.
SP_COPY_OEMINF_CATALOG_ONLY The specified INF file's corresponding catalog files is copied to %windir%\Inf. If this flag is specified, the destination filename information is entered upon successful return if the specified INF file already exists in the Inf directory.
DestinationInfFileName
[out, optional] Pointer to a buffer to receive the INF file name assigned to it at the time it was copied to the INF directory. The buffer, if specified, should typically be MAX_PATH in length. If the SP_COPY_NOOVERWRITE flag is specified and the SetupCopyOEMInf function fails with a return code of ERROR_FILE_EXISTS, this buffer will contain the name of the existing INF file. If the SP_COPY_OEMINF_CATALOG_ONLY flag is specified, this buffer will contain the destination INF filename if the INF file is already present in the INF directory. Otherwise, this buffer will be set to the empty string. This parameter can be NULL.
DestinationInfFileNameSize
[in] Size of the DestinationInfFileName buffer, in characters, or zero if the buffer is not specified. If DestinationInfFileName is specified and this buffer size is less than the size required to return the destination INF filename (including full path), this function will fail. In this case GetLastError will return ERROR_INSUFFICIENT_BUFFER.
RequiredSize
[out, optional] Pointer to a variable that receives the size (in characters) required to store the destination INF file name including a terminating NULL. If the SP_COPY_OEMINF_CATALOG_ONLY flag is specified, this variable will receive a string length only if the INF file already exists in the INF directory. Otherwise, this variable will be set to zero. This parameter can be NULL.
DestinationInfFileNameComponent
[out, optional] Pointer to a string that is set upon successful return (or ERROR_FILE_EXISTS) to point to the beginning of the filename component of the path stored in the DestinationInfFileName parameter. If the SP_COPY_OEMINF_CATALOG_ONLY flag is specified, the DestinationInfFileName parameter may be an empty string. In this case, the character pointer will be set to NULL upon successful return. This parameter can be NULL.

Return Values

TRUE
The SetupCopyOEMInf function succeeded.
FALSE
The SetupCopyOEMInf function failed. For extended error information, call GetLastError.

Remarks

The SetupCopyOEMInf function copies a specified INF file into the %windir%\Inf directory. SetupCopyOEMInf does not recopy the file if it finds that a binary image of the specified INF file already exists in the INF directory with the same name or a name of the form OEM*.INF. When SetupCopyOEMInf copies a file, it renames the copied file to OEM*.INF. Name provided is unique and cannot be predicted.

SetupCopyOEMInf uses the following procedure to determine if the INF file already exists in the INF directory:

All INF files with names of the form OEM*.INF are enumerated and any files that have the same file size as the specified INF file are binary compared.

The INF directory is searched for the source filename of the INF file. If an INF file of the same name exists and is the same size as that of the specified INF file, the two files are binary compared to determine if they are identical.

If the specified INF file already exists a further check is performed to determine if the specified INF file contains a CatalogFile= entry in its [Version] section. If it does, the INF files's %windir%\Inf primary filename with a ".CAT" extension is used to determine if the catalog is already installed. If there is a catalog installed, but it isn't the same as the catalog associated with the source INF, this is not considered to be a match and enumerations continue. It is possible to have multiple identical INF files with unique catalogs contained in %windir%\Inf directory. If an existing match is not found, the INF and CAT files are installed under a new and unique name.

OEM INFs that don't specify a CatalogFile= entry are considered invalid with respect to digital signature verification.

In cases where the INF file must be copied to the %windir%\Inf directory, any digital signature verification failures are reported

If the INF and CAT files already exist, these existing filenames are used and the file replacement behavior is based on the specified CopyStyle flags. Replacement behavior refers only to the source media information stored in the PNF. Existing INF, PNF, and CAT files are not modified.
Requirements
Client Requires Windows XP or Windows 2000 Professional.
Server Requires Windows Server 2003 or Windows 2000 Server.
Header

Declared in Setupapi.h.
Library

Link to Setupapi.lib.
DLL Requires Setupapi.dll.
Unicode

Implemented as SetupCopyOEMInfW (Unicode) and SetupCopyOEMInfA (ANSI).
See Also

Overview, Functions

Last updated: June 2005 | What did you think of this topic? | Order a Platform SDK CD
© Microsoft Corporation. All rights reserved. Terms of use.