1. 11 Ara, 2014 4 kayıt (commit)
    • Noel Grandin's avatar
      java: reduce visibility of fields and methods · 7557f23b
      Noel Grandin yazdı
      found by PMD
      
      Change-Id: Id6737916b68ccbdbdeec5d314747a38410923ac6
      Reviewed-on: https://gerrit.libreoffice.org/13409Tested-by: 's avatarLibreOffice gerrit bot <gerrit@libreoffice.org>
      Reviewed-by: 's avatarNoel Grandin <noelgrandin@gmail.com>
      7557f23b
    • Kohei Yoshida's avatar
      Deteremine the script type of source cell during paste replication. · 808fd5fb
      Kohei Yoshida yazdı
      Doing this ahead of time eliminates the need to update script types of
      all replicated cells after the paste.  This makes significant performance
      impact.
      
      Change-Id: Ic4f7d7b2fe152bd5640ddb1dae01cc2ed757657e
      808fd5fb
    • Tor Lillqvist's avatar
      fdo#87030: Generate a proper PKCS#7 signature · 6e917637
      Tor Lillqvist yazdı
      The signature should be in DER-encoded PKCS#7 format and what CryptSignHash()
      produces is nothing like that. Luckily CryptSignMessage() is actually almost
      easier to use and is capable of doing what we need. This also means that we
      won't need any HCRYPTPROV or HCRYPTHASH after all so all the code related to
      that can be removed. CryptSignMessage() handles both calculating the hash and
      signing it.
      
      One less than ideal issue with CryptSignMessage() is that it needs all the
      data to be hashed and signed at the same time, so we need to keep both buffers
      around for signing.
      
      It also turns out that we don't need to look up the certificate anew from the
      user's certificate store after all.
      
      Now Adobe Reader doesn't complain any longer about the signature's format and
      contents.
      
      Change-Id: I25cfb93b516ffa723c6228d068d9ffa8e7cc4790
      6e917637
    • Tor Lillqvist's avatar
      fdo#87030: Prevent PDF signing using Windows API from failing · 070c93af
      Tor Lillqvist yazdı
      There was one details that I had missed in my initial coding:
      CryptAcquireContext() doesn't give you a HCRYPTPROV key container that
      would contain the private key of a public key certificate. For that
      you need to use CryptAcquireCertificatePrivateKey(). When the hash has
      been created using such a HCRYPTPROV, the CryptSignHash() call
      succeeds.
      
      The certificate in DER encoding that is passed in from the caller,
      obtained in the certificate chooser (in xmlsecurity), is possibly not
      good enough to be used for the other things. So look the same (?)
      certificate up in the user's key store instead. At least more
      properties are present in the certificate when looked up like that.
      
      Add more SAL_INFO logging, with cleartext dumping of certificate
      context property names and list of algorithms supported by the CSP.
      
      Unfortunately, even if all the WinCrypt API calls now succeed, the
      signatures we produce still are not good enough for Adobe Reader... A
      lot of information must be missing, they are quite short, just 256
      bytes.
      
      Change-Id: Ifa4dd37b6d40932fcdcbb07e00c9eb52d54a5477
      070c93af
  2. 10 Ara, 2014 36 kayıt (commit)