Monday, June 25, 2012

SQL Import problems with Sample Data Package for Magento

If you download the Sample Data Package for Magento and use a MySQL server is less than 5.1, it can be when importing the SQL script come to the following SQL error:

niskia:/xxx1# mysql -u magento1 -pXXXXX --database=magento1 < magento_sample_data_for_1.6.1.0.sql
ERROR 1064 (42000) at line 8354: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'USING BTREE, KEY `FK_TAG_FIRST_CUSTOMER_ID_CUSTOMER_ENTITY_ENTITY_ID` (`first_' at line 7

To go beyond this, you have 2 options - to manually fix the error in SQL file, OR to download patched file.

Thursday, June 21, 2012

Error "failed to get a socket for (null)" after upgrading apache httpd

The symptom: After an regular Debian update, when I tried to start apache, it show me this error:

(22)Invalid argument: alloc_listener: failed to get a socket for (null)
Syntax error on line xx of /etc/apache2/ports.conf:

The line was
Listen 80

Wednesday, June 20, 2012

Status on verification of signed file

Digital Signature Status Values
ValidThe signed data and the attached signature data have not been changed since the data was signed. The signature verification operation was successful.
InvalidThe signed data or the attached signature data has been tampered with.
ErrorThe data contained in the Signature element or the signature template itself is malformed, or some other error occurred during verification. In other words, the signature is cryptographically valid, but either it does not conform to the XML Signature standard, or it contains data in a format that InfoPath does not support.
RevokedThe digital certificate used to sign the data has been revoked.
Not TrustedThe digital certificate used to sign the data is not trusted, because no chain of trust can be identified.
ExpiredThe digital certificate used to sign the data is expired.

Counter-signatures and signing a file with multiple certificates

Counter-signing is the action of signing data that includes another signature. Counter-signing requires that signatures have a precise sequence in which they can be deletedwithout invalidating the other signatures. Adding the first signature to a set of data signs the data itself. Adding a second signature does not sign the data in the form, but instead signs the first signature. Each additional counter-signature signs the previous signature. If the signed data itself is tampered with, only the first signature in the list becomes invalid; the status of the rest of the counter-signatures remains unchanged. If the data stored with a particular signature (in the Signature element) is tampered with, such as the comments or nonrepudiation information for that signature, then that signature and the following signature become invalid. For a specific set of signable data, only the last signature in the list can be deleted without affecting any of the others. For a set of signable data configured for counter-signatures, no other signatures can be added after a signature with the status other thanValid. That signature must be deleted before additional counter-signatures can be added.

When you enable digital signatures for an entire form, the form users must enter all the data they require before they sign the form. After the first signature is added, all controls in the form and the form's XML Document Object Model (DOM) become read-only, and the text [Signed] appears in the title bar. Other users who open the form cannot enter data; they can only add, remove, or verify counter-signatures.

Tuesday, June 19, 2012

Searching in default maven repository is the default repository for Maven 2 & 3, but many times it is hard to find the project artifactId, groupId and version in it.
In this case I recommend to manually search for it in

Monday, June 11, 2012

log4j in maven project

Adding support for log4j is realized via maven dependency. You have to edit pom.xml file, and add these lines: