Ошибка при проверке 0x80091007 неправильное значение хеша

Форум КриптоПро
 » 
Средства криптографической защиты информации
 » 
КриптоПро ЭЦП (усовершенствованная ЭЦП)
 » 
Не удалось проверить подпись CAdES-XLT1. Ошибка: [Неправильное значение хеша]. Код: [0x80091007].Соо

Форум КриптоПро
 » 
Средства криптографической защиты информации
 » 
КриптоПро ЭЦП (усовершенствованная ЭЦП)
 » 
Не удалось проверить подпись CAdES-XLT1. Ошибка: [Неправильное значение хеша]. Код: [0x80091007].Соо

function SignCreate(thumbprint, dataToSign) {

    let oCertificate;
    let oSigner;
    let oSignedData;
    let sSignedMessage;

    let oStore = cadesplugin.CreateObject("CAPICOM.Store");
    oStore.Open(CAPICOM_CURRENT_USER_STORE, CAPICOM_MY_STORE, CAPICOM_STORE_OPEN_MAXIMUM_ALLOWED);

    let oCertificates = oStore.Certificates.Find(CAPICOM_CERTIFICATE_FIND_SHA1_HASH, thumbprint);

    if (oCertificates.Count == 0) {
        return "Certificate not found: " + thumbprint;
    }

    oCertificate = oCertificates.Item(1);
    oSigner = cadesplugin.CreateObject("CAdESCOM.CPSigner");
    oSigner.Certificate = oCertificate;
    oSigner.TSAAddress = "http://testca.cryptopro.ru/tsp/tsp.srf";

    oSignedData = cadesplugin.CreateObject("CAdESCOM.CadesSignedData");
    oSignedData.ContentEncoding = CADESCOM_BASE64_TO_BINARY;
    oSignedData.Content = dataToSign.replace('data:application/pdf;base64,', '');

    try {
        sSignedMessage = oSignedData.SignCades(oSigner, CADESCOM_CADES_X_LONG_TYPE_1, true);
    } catch (err) {
        return "Failed to create signature. Error: " + GetErrorMessage(err);
    }

    try {
        oSignedData.VerifyCades(sSignedMessage, CADESCOM_CADES_X_LONG_TYPE_1, true);
    } catch (err) {
        alert("Failed to verify signature. Error: " + cadesplugin.getLastError(err));
        return false;
    }

    oStore.Close();
    return sSignedMessage;
}

• Remove From My Forums

• Question

• SCCM 1902

  Peer-Caching Turned On

  Action in SCCM: Created a new application called “Zoom Client for Meetings V1.0” and deployed to “All Windows 10” collection.

  The installation worked on about 1500 devices and caused errors on about 600.

  What I’m seeing on the device:

  Currently what I’m seeing is the device pulls the content from a peer device and creates a temp folder in ccmcache and then the folder disappears from the ccmcache leaving the application not installed.

  CAS log error:

  Failed to do hash verification with preference : 4. Try to verify at next hash algorithm

  Tried these things:

  • Update Content on original Zoom package 
  • Created a copy of the SCCM package and uploaded content – “Zoom Client for Meetings and redeployed to collection.
  • Application Revision History – deleted one of the 2 revisions
  • Re-created brand new source and package in “Zoom Client for Meetings
  • Deleted all content from all 3 x DP’s and re-distributed new package.
  • Excluded files and folders set >included %windir%CCMCache for AV
  • Added 8 machines to test collection this has the client setting for the peer cache turned off — to see if it will force the devices to go to the main dp’s instead
    of the peer devices — still same errors.

  Help?? Something so simple is giving me so much grief this week.

  Any logs on the SCCM server I can check?

  Anything to do with superpeers in the SCCM database?

  • Edited by

    Thursday, December 5, 2019 3:24 AM

• Remove From My Forums

• Question

• SCCM 1902

  Peer-Caching Turned On

  Action in SCCM: Created a new application called “Zoom Client for Meetings V1.0” and deployed to “All Windows 10” collection.

  The installation worked on about 1500 devices and caused errors on about 600.

  What I’m seeing on the device:

  Currently what I’m seeing is the device pulls the content from a peer device and creates a temp folder in ccmcache and then the folder disappears from the ccmcache leaving the application not installed.

  CAS log error:

  Failed to do hash verification with preference : 4. Try to verify at next hash algorithm

  Tried these things:

  • Update Content on original Zoom package 
  • Created a copy of the SCCM package and uploaded content – “Zoom Client for Meetings and redeployed to collection.
  • Application Revision History – deleted one of the 2 revisions
  • Re-created brand new source and package in “Zoom Client for Meetings
  • Deleted all content from all 3 x DP’s and re-distributed new package.
  • Excluded files and folders set >included %windir%CCMCache for AV
  • Added 8 machines to test collection this has the client setting for the peer cache turned off — to see if it will force the devices to go to the main dp’s instead
    of the peer devices — still same errors.

  Help?? Something so simple is giving me so much grief this week.

  Any logs on the SCCM server I can check?

  Anything to do with superpeers in the SCCM database?

  • Edited by

    Thursday, December 5, 2019 3:24 AM

15 фев 2019 03:42 #10601
от bugzi

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

15 фев 2019 04:50 #10608
от bigvolga

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

15 фев 2019 04:57 #10609
от igor1806

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

15 фев 2019 05:11 #10613
от bigvolga

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

15 фев 2019 05:34 #10615
от bugzi

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

17 фев 2019 20:39 #10691
от bugzi

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

17 фев 2019 21:13 — 17 фев 2019 21:13 #10692
от Wmffre

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

17 фев 2019 21:35 #10693
от bugzi

Спасибо сказали: sedkazna

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.

17 фев 2019 22:44 #10694
от bugzi

Пожалуйста Войти или Регистрация, чтобы присоединиться к беседе.