<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sitevatore</title>
    <link>https://lamendo.la/</link>
    <description>Recent content on Sitevatore</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 09 Oct 2015 00:12:03 +0000</lastBuildDate>
    <atom:link href="https://lamendo.la/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Please Stop curl/wget&#39;ing Directly to bash/sh</title>
      <link>https://lamendo.la/2015/10/09/please-stop-curl-wgeting-directly-to-bash-sh/</link>
      <pubDate>Fri, 09 Oct 2015 00:12:03 +0000</pubDate>
      <guid>https://lamendo.la/2015/10/09/please-stop-curl-wgeting-directly-to-bash-sh/</guid>
      <description>&lt;p&gt;Today, we are going to discuss the dangers of sending the output of a curl or wget command directly to your shell. There are already a few examples on why this is dangerous, with a very clear and concise example available &lt;a href=&#34;https://www.seancassidy.me/dont-pipe-to-your-shell.html&#34; target=&#34;_blank&#34;&gt;here&lt;/a&gt; that explains the dangers of connections closing or failing before the transfer is completed. However, I would like to present a much more malicious example. &lt;em&gt;Sinister, even!&lt;/em&gt; I call it &amp;ldquo;The Bait-and-Switch.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Recommended Nginx SSL/TLS Settings</title>
      <link>https://lamendo.la/2014/06/06/recommended-nginx-ssl-settings/</link>
      <pubDate>Fri, 06 Jun 2014 16:24:10 +0000</pubDate>
      <guid>https://lamendo.la/2014/06/06/recommended-nginx-ssl-settings/</guid>
      <description>&lt;p&gt;&lt;strong&gt;UPDATE: 2024-01-12&lt;/strong&gt; - Defaulted to TLSv1.3 and newer OpenSSL options, but left older recommendations commented, just in case.&#xA;&lt;strong&gt;UPDATE: 2019-01-30&lt;/strong&gt; - Added TLSv1.3 recommend ciphers. Also added another XSS prevention header.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Have you seen the recent (and not so recent) OpenSSL/TLS protocol vulnerabilities, and are you worried about securing connections to the Nginx servers you manage?&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;m going to assume you answered &amp;ldquo;yes&amp;rdquo; to that question, as it&amp;rsquo;s unlikely you&amp;rsquo;d end up on this page otherwise. The whole purpose of this post is to share some high-security SSL configuration info for Nginx, so you&amp;rsquo;ve come to the right place.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Generating Random Passwords in Perl</title>
      <link>https://lamendo.la/2013/04/28/generating-random-passwords-in-perl/</link>
      <pubDate>Sun, 28 Apr 2013 21:19:40 +0000</pubDate>
      <guid>https://lamendo.la/2013/04/28/generating-random-passwords-in-perl/</guid>
      <description>&lt;p&gt;Though I&amp;rsquo;ve already created &lt;a href=&#34;https://lamendo.la/2012/07/05/generating-random-passwords-using-your-systems-random-source/&#34;&gt;the same thing in another post&lt;/a&gt; using a Bash function, I had a very important need for a Perl script that produced random strings. Once I got that little script working, I decided to rewrite the original Bash password generator function entirely in Perl. This may not be the most efficient way to hack it up, but I&amp;rsquo;m no Perl monger, so don&amp;rsquo;t expect perfection. This script does work well, however, and requires no additional modules, so it can be run anywhere there is a Perl interpreter.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Generating Random Passwords in Bash Using Your System&#39;s Random Source</title>
      <link>https://lamendo.la/2012/07/05/generating-random-passwords-using-your-systems-random-source/</link>
      <pubDate>Thu, 05 Jul 2012 09:30:21 +0000</pubDate>
      <guid>https://lamendo.la/2012/07/05/generating-random-passwords-using-your-systems-random-source/</guid>
      <description>&lt;p&gt;Today, we will re-invent the wheel with a simple bash function to generate some passwords and a few hashes as well. Why would I bother coding something when several good programs already exist to perform the same functionality? Well, that&amp;rsquo;s simple: I use this most on systems where I cannot install software. Any user that has SSH access can edit their own .bashrc , so I decided since random password generation is a daily task I perform at my job and elsewhere, it made sense to have a good way to generate passwords. There are a few hashes you can use this for as well. This function will generate the hash used for cookie authentication in phpMyAdmin and it will also generate the hashes used to secure authentication via Wordpress (to be used in wp-config.php). Paste this function in its entirety into your .bashrc or /etc/profile , /etc/bashrc , /etc/bash.bashrc (wherever you feel it should go):&lt;/p&gt;</description>
    </item>
    <item>
      <title>Getting Juniper Network Connect to Work on 64-bit Linux</title>
      <link>https://lamendo.la/2012/06/05/getting-juniper-network-connect-to-work-on-64-bit-linux/</link>
      <pubDate>Tue, 05 Jun 2012 21:37:40 +0000</pubDate>
      <guid>https://lamendo.la/2012/06/05/getting-juniper-network-connect-to-work-on-64-bit-linux/</guid>
      <description>&lt;p&gt;So let&amp;rsquo;s say you&amp;rsquo;ve got a Juniper MAG or SRX or similar unit at work that supports SSL VPN. Now let&amp;rsquo;s say you&amp;rsquo;re running 64-bit Linux at home and need to connect to said VPN. I doubt it makes much difference which distro you use, but I&amp;rsquo;m going to assume you&amp;rsquo;re really cool and are using a Debian-based one. So there are a few necessary steps required to get this Java-based VPN client running, and if you follow this tutorial, you&amp;rsquo;ll have it working in no time.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Using Heartbeat to Share a Single Virtual IP (VIP) Between Two Servers</title>
      <link>https://lamendo.la/2012/05/05/using-heartbeat-to-share-a-single-virtual-ip-vip-between-two-servers/</link>
      <pubDate>Sat, 05 May 2012 10:45:08 +0000</pubDate>
      <guid>https://lamendo.la/2012/05/05/using-heartbeat-to-share-a-single-virtual-ip-vip-between-two-servers/</guid>
      <description>&lt;p&gt;Just did a high availability cluster setup a few weeks ago and though the web servers use the traditional heartbeat/ldirectord setup, there needed to be high availability between the two master/master database servers as well.&lt;/p&gt;&#xA;&lt;p&gt;Yes, this can be done with ldirectord for MySQL, but if you also have other services like Memcached, or Redis, etc, you may just want to share a VIP between the servers.&lt;/p&gt;&#xA;&lt;p&gt;This is especially true if you&amp;rsquo;re connecting to these servers internally. Connecting via the VIP will only connect to one server, so this is not a load-balancing setup, but rather simply a high availability solution (failover).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
