Error Cannot Invoke Persits Aspencrypt
support 128-bit encryption? A. Yes if your system has the Microsoft Enhanced Cryptographic Provider installed. For more information, see the task Learn about Windows Cryptography. Q102. Is AspEncrypt subject to U.S. cryptography export restrictions? A. No, as AspEncrypt's cryptographic functionality comes from external modules called Cryptographic Service Providers. It is those modules that may be subject to the export restrictions. Q103. I am interested in the secure mail feature of AspEncrypt. Can I use a mail component other than AspEmail for that? A. No. AspEncrypt and AspEmail were specifically designed to work together to send secure mail. Notice however, that AspEmail's secure mail functionality is free, so you only need to purchase AspEncrypt, not both components. Q104. When I send encrypted mail with AspEncrypt and AspEmail, do file attachments get encrypted as well? A. Yes. The entire message including all attachments gets encrypted. Common Errors Q201. I want to use my certificate to send signed mail, so I am trying to move it to the HKEY_LOCAL_MACHINE section of the registry using the CertMover sample application. However I keep getting the error "Bad Key". Why? A. For a public/private key pair to be movable, it must have been created with the CRYPT_EXPORTABLE flag. Once a key pair is created you cannot set this flag. The only way out is to generate a new (exportable) key pair and apply for a new certificate. We have provided an online form at www.aspencrypt.com/get_cert.htm which will help you with that. Q202. When I callSet Context = CM.OpenContext("mycontainer", True) it sometimes generates the following error. How do I fix that? Persits.CryptoManager.1 error '800a0001' Keyset does not exist A. Windows NT: This is a permission issue. The current user (such as IUSR_xxx) does not have sufficient permissions to access the specified key container in the registry. To fix this problem, open regedt32 (not regedit!), open the hive HKEY_LOCAL_MACHINE and highlight the key HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\MachineKeys\
PS080519170Usage under a 64-bit Server EnvironmentALL 22 Jan 2016 PS150930186HOWTO: Render an image at desired dimensionsAspPDF 30 Sep 2015 PS121023186Using .NET components in classic ASPALL 17 Oct 2013 PS150809184HOWTO: Convert a mutli-page PDF document to multi-image TIFF with AspPDF.NETAspPDF 09 Aug 2015 PS130806188HOWTO: Convert UTF-8 Encoded Strings to Unicode in Classic ASPAspPDF 06 Aug 2013 PS130905190HOWTO: Create a multi-page PDF document from a single-page templateAspPDF 05 Sep 2013 PS01032115ActiveX component http://www.aspencrypt.com/faq.html can't create object / The call to Server.CreateObject failed while checking permissionsALL 09 Dec 2010 PS071016166Retrieving the COM class factory failed due to the following error: 80040154ALL 18 Feb 2014 PS130829189HOWTO: Use Persits Components under PHPALL 24 Oct 2013 PS01032622Invalid class string / Invalid ProgID errorALL 26 Apr 2011 PS120809184Permission denied errorAspEmail http://support.persits.com/?displayall=1 09 Aug 2012 PS120828185HOWTO: Create fixed-size thumbnail while preserving aspect ratioAspJpeg 28 Aug 2012 PS120809182Error 800706be under COM+ (Component Services)ALL 09 Aug 2012 PS02041192HOWTO: Renaming uploaded filesAspUpload 15 Dec 2010 PS01122781503 Need Rcpt command errorAspEmail 09 Feb 2002 PS100721176SendBinary fails under IIS7 on Vista, Windows 2008 and 7AspUpload 22 Mar 2011 PS01032724550 Relaying Denied errorAspEmail 23 Feb 2012 PS130411187SYSTEM: CONFIG: No DNS Server found errorAspEmail 11 Apr 2013 PS101117178530 5.7.0 Must issue a STARTTLS command first errorAspEmail 22 Nov 2010 PS120123181Thumbnails of PNG images contain unexpected background patternsAspJpeg 04 Mar 2013 PS01041237Connection refused errorAspEmail 20 Oct 2011 PS02010782HTTP 500 - Internal server errorALL 29 Oct 2014 PS02062099The system cannot find the file specified error when saving to a wwwroot subdirectoryAspUpload 20 Jun 2002 PS080121169HOWTO: Determine form field namesAspPDF 21 Jan 2008 PS120809183Content-Type header could not be obtained error under ASP.NETAspUpload 09 Aug 2012 PS100817177BUG: Object number not found in object header errorAspPDF 17 Au
8.3 Digital Signing 8.4 Client-Side Signing of Server-Side PDFs 8.5 PDF-based Secure Mail 8.1 Overview of PDF Security A secure PDF is a document that imposes a set of restrictions on this document’s user, such as requiring a password on opening, or preventing copying/pasting of the document’s content. There are two aspects to the standard (or built-in) PDF security: password protection and permission flags. 8.1.1 Password Protection When a secure PDF is created, the document author supplies two secret strings: the Owner and User passwords. Applying these two passwords to the document using an algorithm described in Adobe PDF specifications produces a secure document. A secure PDF’s content is encrypted with the RC4 algorithm, a stream cipher invented by Ron Rivest of RSA Security. Either a 40-bit or 128-bit key can be used. As of AspPDF 2.2, the 128-bit Advanced Encryption Standard (AES) cipher is also supported. An encryption key is derived from the user password alone. The owner password is used to encrypt the user password and also to protect the immutability of the document’s permission flags. An encrypted copy of the user password is embedded in a secure PDF for validation purposes. To open an encrypted document, the viewer must specify either the user or owner password. Specifying the valid user password enables a user to view the document, but also makes her subject to the permission flags associated with the document. For example, a user may not be able to modify or print the document. Specifying the valid owner password gives the user full control over the document: not only can she view it, but also change or remove its security settings. An empty string is a perfectly valid value for either password. There are 4 possible password use scenarios: Scenario 1: Both user and owner passwords are non-empty and not equal to each other. A user must specify a password to open the document. Use this scenario to create private password-protected documents with certain usage restrictions imposed, such as "no printing". If the two passwords are the same, the owner password is ignored and this turns into Scenario 3. Scenario 2: The owner password is non-empty, the user password is empty. The document can be viewed without specifying a password, but a user is subject to permission flags. Use this scenario to create publicly accessible documents with certain usage restrictions imposed. Scenario 3: The owner password is empty, t