

<feed xmlns="http://www.w3.org/2005/Atom">
  <id>https://picolino.dev/</id>
  <title>Danila Chervonny</title>
  <subtitle>picolino</subtitle>
  <updated>2025-04-14T03:07:24+03:00</updated>
  <author>
    <name>Danila Chervonny</name>
    <uri>https://picolino.dev/</uri>
  </author>
  <link rel="self" type="application/atom+xml" href="https://picolino.dev/feed.xml"/>
  <link rel="alternate" type="text/html" hreflang="en"
    href="https://picolino.dev/"/>
  <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator>
  <rights> © 2025 Danila Chervonny </rights>
  <icon>/assets/img/favicons/favicon.ico</icon>
  <logo>/assets/img/favicons/favicon-96x96.png</logo>


  
  <entry>
    <title>Generate personal CA and certificates for client auth</title>
    <link href="https://picolino.dev/posts/auth-using-certificate/" rel="alternate" type="text/html" title="Generate personal CA and certificates for client auth" />
    <published>2022-09-17T00:00:00+03:00</published>
  
    <updated>2023-04-23T00:00:00+03:00</updated>
  
    <id>https://picolino.dev/posts/auth-using-certificate/</id>
    <content type="text/html" src="https://picolino.dev/posts/auth-using-certificate/" />
    <author>
      <name>Danila Chervonny</name>
    </author>

  
    
    <category term="Certificates" />
    
  

  <summary>Create Root CA (Done once)

Create Root Key

Attention: this is the key used to sign the certificate requests, anyone holding this can sign certificates on your behalf. So keep it in a safe place!

openssl genrsa -des3 -out rootCA.key 4096


Create and self sign the Root Certificate

openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 1024 -out rootCA.crt


Here we used our root key to ...</summary>

  </entry>

  
  <entry>
    <title>GitHub Actions: Setup Check-In build</title>
    <link href="https://picolino.dev/posts/setup-check-in-build/" rel="alternate" type="text/html" title="GitHub Actions: Setup Check-In build" />
    <published>2020-10-18T00:00:00+03:00</published>
  
    <updated>2023-04-23T00:00:00+03:00</updated>
  
    <id>https://picolino.dev/posts/setup-check-in-build/</id>
    <content type="text/html" src="https://picolino.dev/posts/setup-check-in-build/" />
    <author>
      <name>Danila Chervonny</name>
    </author>

  
    
    <category term="GitHub Actions" />
    
  

  <summary>In this article we gonna create continious integration check-in build using GitHub Actions that will be launched at every new commit or pull request in specific branches.



Create build workflow

All you need to do is to create new .yml file at your repository:

{YOUR_PROJECT}/.github/workflows/check-in.yml


With that content:

name: Check-in

env:
  GITHUB_TOKEN: ${{ github.token }}  # set t...</summary>

  </entry>

  
  <entry>
    <title>GPG: Files validation with GPG and SHA</title>
    <link href="https://picolino.dev/posts/gpg-signing/" rel="alternate" type="text/html" title="GPG: Files validation with GPG and SHA" />
    <published>2020-03-27T00:00:00+03:00</published>
  
    <updated>2020-08-07T00:00:00+03:00</updated>
  
    <id>https://picolino.dev/posts/gpg-signing/</id>
    <content type="text/html" src="https://picolino.dev/posts/gpg-signing/" />
    <author>
      <name>Danila Chervonny</name>
    </author>

  
    
    <category term="GPG" />
    
  

  <summary>Here are some tips on how to secure and validate files using GPG and certutil in Windows.



Signing

You can sign files using GPG. The command below adds a new file with .asc postfix contains a target file signature.

gpg --detach-sign --armor SomeZipFile.zip


If you want other people to have the opportunity to verify files was signed by your GPG key - you need to share public GPG key to them...</summary>

  </entry>

  
  <entry>
    <title>GPG: Share existing GPG key</title>
    <link href="https://picolino.dev/posts/gpg-token-share/" rel="alternate" type="text/html" title="GPG: Share existing GPG key" />
    <published>2020-03-26T00:00:00+03:00</published>
  
    <updated>2023-04-23T00:00:00+03:00</updated>
  
    <id>https://picolino.dev/posts/gpg-token-share/</id>
    <content type="text/html" src="https://picolino.dev/posts/gpg-token-share/" />
    <author>
      <name>Danila Chervonny</name>
    </author>

  
    
    <category term="GPG" />
    
  

  <summary>If you have an existing registered GPG key and GitHub account configured to use it so you can share it across multiple machines.



Export existing GPG key

First of all, you need to export the existing GPG key by using this command:

gpg --export-secret-key --armor &amp;amp;gt; secretkey.asc


Then enter your key’s secret passphrase in prompt dialog.

This will export your key to secretkey.asc file in...</summary>

  </entry>

  
  <entry>
    <title>GPG: Setup GPG key for GitHub</title>
    <link href="https://picolino.dev/posts/gpg-token-setup/" rel="alternate" type="text/html" title="GPG: Setup GPG key for GitHub" />
    <published>2020-03-25T00:00:00+03:00</published>
  
    <updated>2023-04-23T00:00:00+03:00</updated>
  
    <id>https://picolino.dev/posts/gpg-token-setup/</id>
    <content type="text/html" src="https://picolino.dev/posts/gpg-token-setup/" />
    <author>
      <name>Danila Chervonny</name>
    </author>

  
    
    <category term="GPG" />
    
  

  <summary>GitHub uses the GPG key to ensure user who committed into a repository is the same person.

GitHub marks such commits as verified so other people can trust that the changes in verified commit came from a trusted source.



This instruction is about how to set up a GPG key to making all commits into GitHub repository secured and verified.



Install GPG utilities


  Install GPG CLI.
  
    Add ...</summary>

  </entry>

</feed>


