Skip to main content

Keystore Errors and possible causes

You might have played with the keystore and java security objects many times.Some of these errors happen when you install it first time

# Java's default cacerts password is "changeit", unless you're on a Mac, where it's "changeme".
 # Better to execute it as root, hence sudo su
 sudo su - -c /usr/java6_64/bin/keytool -import -trustcacerts -file /tmp/ServerCertficate.crt -keystore /usr/java6_64/jre/lib/security/cacerts -alias diaryfolio_Certificate

#No need of any password while viewing (Just press enter)
 /usr/java6_64/bin/keytool -list -v -keystore /usr/java6_64/jre/lib/security/cacerts   >/tmp/java6.abc

Common Errors

1.  Keytool Error with Java lang Exception

 keytool error: java.lang.Exception: Input not an X.509 certificate

This may be caused due to
- Not specifying an alias name correctly?
- Space or incorrect blanks
- Check in the certificate (.crt file), if there are any headers or footers before
 —–BEGIN CERTIFICATE—–


or anyting after
 —–END CERTIFICATE—–

SolutionRemove entries after head and footers and try importing again

 2.  Keytool Error with Java Filenotfound Exception

keytool error (likely untranslated): java.io.FileNotFoundException: /usr/java6_64/jre/lib/security/cacerts (Permission denied)

Solution:This happens because you don't have edit permission (or insert) for the keystore. Run as root.

 3.  Keytool Error with Java IO Exception

 keytool error (likely untranslated): java.io.IOException: Keystore was tampered with, or password was incorrect

Solution: Ensure the password is correct. Try  password "changeit"  (as it is the default) or the password might have been changed by someone. In which case contact your OS admin having root access and try to export the keytool entries as exporting doesn't require password. (Step at top of this page). Carefully find the entries which you feel is required for your organisation, later create a cacerts file of your own and import these custom entries.

Popular posts from this blog

Syslog Standards: A simple Comparison between RFC3164 & RFC5424

Syslog Standards: A simple Comparison between RFC3164 (old format) & RFC5424 (new format) Though syslog standards have been for quite long time, lot of people still doesn't understand the formats in detail. The original standard document is quite lengthy to read and purpose of this article is to explain with examples Some of things you might need to understand The RFC standards can be used in any syslog daemon (syslog-ng, rsyslog etc.) Always try to capture the data in these standards. Especially when you have log aggregation like Splunk or Elastic, these templates are built-in which makes your life simple. Syslog can work with both UDP & TCP  Link to the documents the original BSD format ( RFC3164 ) the “new” format ( RFC5424 ) RFC3164 (the old format) RFC3164 originated from combining multiple implementations (Year 2001)

Create your own Passport Photo using GIMP

This tutorial is for semi-techies who knows a bit of GIMP (image editing).   This tutorial is for UK style passport photo ( 45mm x 35 mm ) which is widely used in UK, Australia, New Zealand, India etc.  This is a quick and easy process and one can create Passport photos at home If you are non-technical, use this link   .  If you want to create United States (USA) Passport photo or Overseas Citizen of India (OCI) photo, please follow this link How to Make your own Passport Photo - Prerequisite GIMP - One of the best image editing tools and its completely Free USB stick or any memory device to store and take to nearby shop A quality Digital camera Local Shops where you can print. Normally it costs (£0.15 or 25 US cents) to print 8 photos Steps (Video Tutorial attached blow of this page) Ask one of your colleague to take a photo  of you with a light background. Further details of how to take a photo  yourself       Take multiple pictures so that you can choose from th

Elastic Beats on pfSense : Installation and configuration

Summary Though in many cases syslog is preferred to transport the pfSense logs to external system, Elastic beats provides quite a niche way to send the logs while modelling the data alongside. This makes it ready-made to send to ElasticSearch directly and get ready-made outcomes like SIEM, performance etc. Pre-reqs A build server (preferably Ubuntu or Fedora) with internet connectivity shell access to pfsense server Basic knowledge of Elastic Stack (filebeat.yml configurations etc) Ensure connectivity is allowed from pfsense machine to your Elastic Stack receiver Setup Summary Connectivity tests Install dependencies in build server (vagrant, virtualbox, gmake, go etc) Download Elastic Beats source Make elastic Beats package for FreeBSD Copy binary packages to pfsense server Configure Beats to send to destination Configure ElasticSearch to view the data Installation Steps Connectivity tests Logon to pfsense server via Shel