/usr/share/doc/sadms/html/acls-tut-remote.html is in sadms 2.0.15.repack-0ubuntu2.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 | <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>pygtk-fsacls</title>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta http-equiv="Content-Language" content="en-us">
<link rel="stylesheet" href="sadms.css" type="text/css">
</head>
<body>
<table width="100%" border="0">
<tr>
<td><div align="left"><img src="images/pygtk-fsacls.gif" width="97" height="92"></div></td>
<td><div class="section-title" align="right">remote</div></td>
</tr>
</table>
<table width="100%" border="0" cellpadding="5">
<tr>
<td colspan="2"><p>Remote operation involves running pygtk-fsacls on a remote host while preserving the GUI interface on the local host.<br>
First off, to enable remote operation of pygtk-fsacls, the pygtk-fsacls suite has to be exported to the remote host.</p>
</td>
</tr>
<tr>
<td width="38%"><img src="images/remote-remote0.png" width="453" height="331"></td>
<td width="62%"><p>The <strong>Remote</strong> panel controls : </p>
<ul>
<li>Whether remote operation is enabled </li>
<li>The target remote host.</li>
<li>The user to connect as.</li>
<li>The working directory to operate in.</li>
</ul></td>
</tr>
<tr>
<td><img src="images/remote-key0.png" width="453" height="331"></td>
<td><p>The <strong>Settings</strong> panel controls the settings of the ssh link that is used for remote operation.</p>
<p>The Keys panel determines which key is used.</p>
<p>First a private/public key pair has to be generated. </p></td>
</tr>
<tr>
<td><img src="images/key-password.png" width="218" height="134"></td>
<td>The key has a password attached to it to protect its use.</td>
</tr>
<tr>
<td><img src="images/remote-key.png" width="453" height="331"></td>
<td>The keys have been generated. </td>
</tr>
<tr>
<td><img src="images/remote-agent0.png" width="453" height="331"></td>
<td>The agent reads --loads- the key once. This requires providing the agent the key's password. When later operations require the key it is transparently handed over to the requesting process. </td>
</tr>
<tr>
<td><img src="images/remote-agent.png" width="453" height="331"></td>
<td><p>The key has been loaded.</p>
<p>If the key has just been generated, the password has been cached and will not be asked again. If not the key's password will be asked. </p></td>
</tr>
<tr>
<td><img src="images/remote-remotekey0.png" width="453" height="331"></td>
<td>The public key has to be exported to the remote host for it to encrypt communication with the localhost. If you know the key to have been exported you can skip the export stage as the export is valid once for all.</td>
</tr>
<tr>
<td><img src="images/ssh-password.png" width="218" height="154"></td>
<td>To export the key, ssh/scp will be used. As the ssh/scp transfers are not --yet-- automated this step will require the sh password of the remote host's root user.</td>
</tr>
<tr>
<td><img src="images/remote-remotekey.png" width="453" height="331"></td>
<td>The public key has been exported to the remote host. You can also retrieve this public key, to make sure. </td>
</tr>
<tr>
<td><img src="images/remote-run.png" width="453" height="331"></td>
<td>Automated remote operation is now possible. You can test it by running a standard program such as <em>id</em> or <em>hostname</em> </td>
</tr>
<tr>
<td><img src="images/remote-remote.png" width="453" height="331"></td>
<td>Automated remote operation is now possible. Check <strong>Remote operations</strong> to enable them. </td>
</tr>
</table>
<p> </p>
</body>
</html>
|