<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Musl on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/musl/</link>
    <description>Recent content in Musl on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 23 Feb 2018 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/musl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Creating Static Binaries for Nmap, Socat and other Tools</title>
      <link>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</link>
      <pubDate>Fri, 23 Feb 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/02/creating-static-binaries-for-nmap-socat-and-other-tools/</guid>
      <description>&lt;p&gt;In various scenarios it might be helpful or even required to have a statically compiled version of Nmap available. This applies to e.g. scenarios where only limited user privileges are available and installing anything to the system might not be desirable.&lt;/p&gt;&#xA;&lt;p&gt;For such cases I’ve started to create recipes to build such binaries. Similar projects are already available on GitHub, but there are several reasons why I chose to create my own tools:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
