<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Authorized_keys on BAFM</title><link>https://christian.blog.pakiheim.de/tags/authorized_keys/</link><description>Recent content in Authorized_keys on BAFM</description><generator>Hugo -- 0.160.1</generator><language>en</language><lastBuildDate>Fri, 08 Aug 2014 08:29:59 +0000</lastBuildDate><atom:link href="https://christian.blog.pakiheim.de/tags/authorized_keys/index.xml" rel="self" type="application/rss+xml"/><item><title>NetApp FAS/Data ONTAP public key authentification with CIFS/NFS license</title><link>https://christian.blog.pakiheim.de/posts/2014-08-08_netapp-fas-data-ontap-public-key-authentification-with-cifs-nfs-license/</link><pubDate>Fri, 08 Aug 2014 08:29:59 +0000</pubDate><guid isPermaLink="false">http://blog.barfoo.org/?p=4220</guid><description>&lt;p&gt;Well as the title says, sadly we bought our FAS6210 without CIFS/NFS license. Thus, in order to create the folder structure/add the &lt;em&gt;authorized_keys&lt;/em&gt; file, you&amp;rsquo;ll have to work for your money a little bit.&lt;/p&gt;
&lt;p&gt;First, you need to run &lt;em&gt;cifs setup&lt;/em&gt; / &lt;em&gt;cifs passwd&lt;/em&gt; somewhere. I did it on our Data ONTAP simulator, which comes in handy for things like that.&lt;/p&gt;
&lt;p&gt;You&amp;rsquo;ll get a cryptic looking password (no clue which format that is), looking like this: _OnWddr)xa.&lt;/p&gt;</description></item></channel></rss>