Skip to main content

RootCA, IntermediateCA basics

 Certificates are issued by maintaining chain of trust. Your certificate can be signed by either root ca or intermediate ca. Both of them use their private key to sign your certificate. When intermediate ca signs your certificate then it is doing that on behalf of root ca in order to off-load root ca's tasks. 

As intermediate ca signs your web server certificate, like the same way root ca signs intermediate ca's certificate so that web browser can verify that by using root ca's public key. 

Once the web server certificate is signed then a certificate bundle is created in which root ca's certificate, intermediate ca's certificate and web server's certificate are send to the organization owner who owns the web server. 

Note: OS, browsers already contains the root ca or intermediate ca's public key or certificate.

Sometimes the certificate bundle is send by the web server so that browser easily verify intermediate ca and root ca. 

Web browser checks web server's certificate by extracting the public key of intermediate ca from the certificate. As web server certificate is signed by intermediate ca so web server's certificate contains intermediate ca's public key. Once it is assured that web server certificate is valid then it is go for checking intermediate ca's certificate is ok or not by extracting the public key of root ca. As root ca signed intermediate ca's certificate, so it shall also found ok. Here used asymmetric algorithm.  

After that secure communication starts by generating secret, master secret and finally session keys. Here used symmetric algorithm for faster communication. 


Avi

Comments

Post a Comment

Popular posts from this blog

Installing Codename SCNR web application scanner on ubuntu | kali

  Perform the following steps from a non-root user. We will go for manual installation.  https://github.com/scnr/installer?tab=readme-ov-file#manual-installation https://github.com/scnr/installer/releases wget https://github.com/scnr/installer/releases/download/v1.7.3/scnr-v1.7.3-linux-x86_64.tar.gz   (Download using normal user) tar -xvzf scnr-v1.7.3-linux-x86_64.tar.gz cd scnr-v1.7.3 cd bin Now go to their website ( https://ecsypno.com/products/scnr ) and subscribe for community edition license from your official email.  ./scnr_activate 6XQ97FW3LVBECD0UJ5H214 ./scnr https://www.example.net/Login.aspx --system-slots-override Now they generate .ser format report after testing the application by default which is hard to read. We need html report. So for example, to generate an HTML report: ./scnr_reporter --report=html:outfile=my_report.html.zip /home/user/.scnr/reports/report.ser Avi
Post a Comment
Read more

API hacking lab setup

 Follow the commands to install and configure API hacking lab: 1. Install kali linux and update all the packages.  apt update -y apt upgrade -y or apt dist-upgrade -y or apt full-upgrade -y If you face any problem regarding update, install cloud flare warp in the host machine, then again start updating packages in your kali vm.  2. Install and configure burpsuite professional.  After that open burpsuite and go to Extensions tab. Click on BAppStore. Search for Autorize extension, It will help us to automate authorization testing. Click on Download Jython from the right side. From Jython website click on Jython standalone JAR and save it. Go to Extensios > Extensions settings >  under Core extension settings find out Python environment on the right pane. Select the jython jar file that you just downloaded. Now again go to BAppStore and re-search for Autorize extension. You will see Install option this time after selecting Autorize extension. Install it. You ...
Post a Comment
Read more

Install Nessus from docker

Docker installation. Give the below commands one by one. apt install docker-cli or apt install docker.io After the installation is complete, if you are inside wsl then give this command to start docker, because inside wsl systemd (systemctl) does not work: service docker start WSL troubleshooting : If the above command " service docker start " does not work then use below command: dockerd (It may not work if any previous docker process is running. It will show you pid of that process. Use this command to kill that process " kill -9 pid " and run dockerd command again) If " docker ps -a " giving error like " Cannot connect to the Docker daemon at unix:///run/podman/podman.sock. Is the docker daemon running? " This is because you may installed podman-docker package. If you remove the package still you will get this error but you should remove the package. Then issue this command: env | grep -i docker DOCKER_HOST=unix:///run/podman/podman.sock   --...
Post a Comment
Read more