peteyboy/tutes-dump
2
1
Fork 0
forked from pifty/tutes-dump
Code Issues Pull Requests Projects Releases Wiki Activity

Replace escape <,> with <, >

Browse Source 
for i in *.html.docuwiki; do perl -pi -e "s/&gt;/>/g" $i; done
for i in *.html.docuwiki; do perl -pi -e "s/&lt;/</g" $i; done
This commit is contained in:
peteyboy
2021-03-11 23:50:37 +00:00
parent 11889ecf9e
commit c81979dcbf
63 changed files with 573 additions and 573 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dump/SSH_Key_Authentication.html.docuwiki
+1 -1
View File
@@ -18,7 +18,7 @@ You can then add a passphrase to your key, and use just that one passphrase when
The key comment is for your personal convenience, I reccomend youruser@yourlocalmachine and maybe the date, but of course it's up to you. Now save both the private and public key file somewhere (My Documents is a good choice, but pick somewhere that only *you* will have read access to.)
Next, you need to configure PuTTY to use this key. Fire up PuTTY and load your session or create a new one. Then in the Category list on the left, selecct Connection &gt; SSH &gt; Auth. Browse for your key and load it up. Also, you'll want to allow changes of username if your SDF account name is different from your local one.
Next, you need to configure PuTTY to use this key. Fire up PuTTY and load your session or create a new one. Then in the Category list on the left, selecct Connection > SSH > Auth. Browse for your key and load it up. Also, you'll want to allow changes of username if your SDF account name is different from your local one.
You're almost done! Now you need to let the server know about your new key. After you do this, the ssh, scp and sftp programs will use the key files automatically. So (optionally, but it is recommended) save your session, and then connect. Now do the following to authorize your key: