<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>security on nidomiro</title>
    <link>https://nidomiro.de/tags/security/</link>
    <description>Recent content in security on nidomiro</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 21 Aug 2020 12:00:00 +0000</lastBuildDate><atom:link href="https://nidomiro.de/tags/security/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>More secure deployments via ssh</title>
      <link>https://nidomiro.de/code/more-secure-deployments-via-ssh/</link>
      <pubDate>Fri, 21 Aug 2020 12:00:00 +0000</pubDate>
      
      <guid>https://nidomiro.de/code/more-secure-deployments-via-ssh/</guid>
      <description>If we deploy an application automatically we have to grant the CI (Continuous Integration) access to the server. Common practice is to do that via a GitLab Runner or a ssh account on the server.
Personally I would not recommend to use a GitLab Runner for deployments, because you have to maintain it. Another potential issue is, that you normally register runners for your whole GitLab instance or groups. That results in a scenario in which everyone can use that runner and accidentally (or not) destroy, for example, your production server.</description>
    </item>
    
  </channel>
</rss>
