Skip to main content

Create A Digital Certificate


Here is the way to - HOWTO - create a Digital Certificate using OpenSSL software. First of all install OpenSSL on you PC. 


Create your Own CA 
Then create some directory to be your CA directory (let's call it demoCA) 
Now create the following 3 directories in demoCA (requests, certs, and keys) and create the following to files (database.txt, and serial.txt) and open serial.txt and write 01 in it. Also don't forget to copy the file openssl.conf there too. 
Now you need to create your CA key: 
 openssl genrsa -des3 -out keys/ca.key 1024 
Create a master certificate based on this key, to use when signing other certificates: 
 openssl req -config openssl.conf -new -x509 -days 1001 -key keys/ca.key -out certs/ca.cer

Create the Digital Certificate 
Generate private key for the certificate: 
 openssl genrsa -des3 -out keys/foo-key.pem 2048 
Create a certificate request: 
 openssl req -new -key keys/foo-key.pem -out requests/foo-req.csr
Sign the certificate by the CA: 
 openssl ca -policy policy_anything -config openssl.conf -cert certs/ca.cer -in requests/foo-req.csr -keyfile keys/ca.key -days 3650 -out certs/foo-cert.cer
Convert the certificate format to x509 to be used by Windows Internet Explorer 
 openssl x509 -in certs/foo-cert.cer -out certs/foo-cert-509.cer

Comments

Popular posts from this blog

Hacking Windows 10 UWP App: DLL Injection & common Vulnerabilities

I recently started working on  widows 10 Apps( Apps not Applications) security. Before diving deep in hacking terms lets try to understand what's new in Windows 10 UWP( Universal Platform) as compared to old Apps. Lets begin with how apps actually work on windows 10(desktop/tablet). Now windows 10 comes with a container only for running apps inside the isolated environment. By default, /APPCONTAINER(Linker Flag) is off. This option modifies an executable to indicate whether the app must be run in the appcontainer process-isolation environment. Specify /APPCONTAINER for an app that must run in the appcontainer environment—for example, a Windows Store app. (The option is set automatically in Visual Studio when you create a Windows Store app from a template.) For a desktop app, specify /APPCONTAINER:NO or just omit the option. The /APPCONTAINER option was introduced in Windows 8. Now there is no registry entry concept for these app in the System HIVE rather they install they own hiv

Jsunpack-n Tutorial (Analyzing Malicious Documents)

INSTALLATION: Required Dependencies(all these dependencies are present in jsunpack-n package in a folder named depend): 1) Build and install pynids (nids) from ./depends/pynids-0.6.1.tar.gz To compile pynids, you may need the following (ubuntu) packages: libpcap-dev pkg-config python-dev libgtk2.0-dev libnet1-dev         To install these package either use software center or command apt-get install PackageName     $ cd depends     $ tar xvfz pynids-0.6.1.tar.gz $ cd pynids-0.6.1/ directory $ python setup.py build $ sudo python setup.py install 2) Build SpiderMonkey 'js' from ./depends/js-1.8.0-rc1-src.tar.gz     This package has modifications to the spidermonkey source code; therefore, it is not recommended you use default smjs packages. (Details of the modifications are in INSTALL.spidermonkey.shellcode and INSTALL.spidermonkey, for historical purposes)     $ cd depends/     $ tar xvfz js-1.8.0-rc1-src.tar.gz     $ cd js-1.8.0-rc1-src     $ mak

SSI Injection Attack

SSIs are directives present on Web applications used to feed an HTML page with dynamic contents. They are similar to CGIs, except that SSIs are used to execute some actions before the current page is loaded or while the page is being visualized. In order to do so, the web server analyzes SSI before supplying the page to the user. The Server-Side Includes attack allows the exploitation of a web application by injecting scripts in HTML pages or executing arbitrary codes remotely. It can be exploited through manipulation of SSI in use in the application or force its use through user input fields. It is possible to check if the application is properly validating input fields data by inserting characters that are used in SSI directives, like:  Code: < ! # = / . " - > and [a-zA-Z0-9] Another way to discover if the application is vulnerable is to verify the presence of pages with extension .stm, .shtm and .shtml. However, the lack of these type of pages does not mean that th