<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Radsecproxy on Nico Maas</title>
        <link>https://www.nico-maas.de/tags/radsecproxy/</link>
        <description>Recent content in Radsecproxy on Nico Maas</description>
        <generator>Hugo -- gohugo.io</generator>
        <language>en-us</language>
        <lastBuildDate>Mon, 27 Jun 2016 11:51:44 +0000</lastBuildDate><atom:link href="https://www.nico-maas.de/tags/radsecproxy/index.xml" rel="self" type="application/rss+xml" /><item>
            <title>[Ubuntu] Radsecproy for secure Radius over WAN</title>
            <link>https://www.nico-maas.de/posts/2016-06-27-ubuntu-radsecproy-for-secure-radius-over-wan/</link>
            <pubDate>Mon, 27 Jun 2016 11:51:44 +0000</pubDate>
            <guid>https://www.nico-maas.de/posts/2016-06-27-ubuntu-radsecproy-for-secure-radius-over-wan/</guid>
            <description>&lt;p&gt;Chances are you going to need an radius Auth over WAN - because your Radius and Identity Mngmnt is hosted in the security of the local datacenter of your corp&amp;hellip; but the client (i.e. an network switch) is somewhere over the &lt;del&gt;rainbow&lt;/del&gt; WAN. You &lt;em&gt;could&lt;/em&gt; just pipe the radius traffic over the internet - but there be dragons: radius communication is unencrypted. So&amp;hellip; just no.&lt;/p&gt;&#xA;&lt;p&gt;Enter radsecproxy: Radsecproxy is - as the name implies, an radius proxy - which needs to be installed on both servers (the local one in your company, now called SERVER, and the remote one with the switch attached, now called CLIENT) - and does encrypt the communication between both server parts (over WAN i.e.) via TLS.&lt;/p&gt;</description>
        </item></channel>
</rss>
