smeserver-remoteuseraccess/contribs8/smeserver-remoteuseraccess-1.2-locale-2008-05-21.patch

--- /dev/null   2008-05-19 14:06:25.237608604 -0600
+++ pootleupdate/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/remoteuseraccess  2008-05-21 02:25:51.000000000 -0600
@@ -0,0 +1,62 @@
+<lexicon lang="bg">
+    <entry>
+      <base>User Remote Access</base>
+      <trans>User Remote Access</trans>
+    </entry>
+    <entry>
+      <base>SSH keys</base>
+      <trans>SSH keys</trans>
+    </entry>
+    <entry>
+      <base>FORM_TITLE</base>
+      <trans>Change user remote access settings</trans>
+    </entry>
+    <entry>
+      <base>SHELL_ACCESS</base>
+      <trans>Shell</trans>
+    </entry>
+    <entry>
+      <base>SUDO</base>
+      <trans>Sudo</trans>
+    </entry>
+    <entry>
+      <base>SSH_KEYS</base>
+      <trans>SSH Keys</trans>
+    </entry>
+    <entry>
+      <base>CHROOT_PATH</base>
+      <trans>Chroot Path</trans>
+    </entry>
+    <entry>
+      <base>CHROOT_PATH_NOT_GIVEN</base>
+      <trans>Chroot Path not given</trans>
+    </entry>
+    <entry>
+      <base>CHROOT_PATH_NON_EXISTANT</base>
+      <trans>Chroot Path does not exist</trans>
+    </entry>
+    <entry>
+      <base>SELECT_CHROOT_PATH</base>
+      <trans>Select Chroot Path</trans>
+    </entry>
+    <entry>
+      <base>VPN_ACCESS</base>
+      <trans>RSSH + VPN Access</trans>
+    </entry>
+    <entry>
+      <base>SHELL_ACCESS</base>
+      <trans>Shell Access</trans>
+    </entry>
+    <entry>
+      <base>SUDOER_ACCESS</base>
+      <trans>Sudo Access</trans>
+    </entry>
+    <entry>
+      <base>MODIFY_DESCRIPTION</base>
+         <trans><![CDATA[ <p> Enabling bash shell access for a user account poses a security risk. Only use this option if you know what you are doing. A safer option is to allow rssh access (sftp, ssh & rsync). </p> <p> Sudo access allows users to execute commands with the permissions of the root account without knowing the root password. This is more desirable than passing around the root password. Setting Sudo to yes also sets the shell to bash </p> <p> SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened. </p> <p> Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field. </p> <p> Enter the public SSH Keys to allow ssh access without passwords, keys should be pasted as a single line, but they will wrap onto three or more lines in the display. To delete all keys type "deletekeys". </p> ]]></trans>
+    </entry>
+    <entry>
+      <base>SSHKEYS_DESCRIPTION</base>
+      <trans>Enter the public SSH Keys to allow ssh access without passwords, keys should be pasted as a single line, but they will wrap onto three or more lines in the display. To delete all keys type "deletekeys".</trans>
+    </entry>
+</lexicon>
1	unnilennium	1.1	--- /dev/null 2008-05-19 14:06:25.237608604 -0600
2			+++ pootleupdate/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/remoteuseraccess 2008-05-21 02:25:51.000000000 -0600
3			@@ -0,0 +1,62 @@
4			+<lexicon lang="bg">
5			+ <entry>
6			+ <base>User Remote Access</base>
7			+ <trans>User Remote Access</trans>
8			+ </entry>
9			+ <entry>
10			+ <base>SSH keys</base>
11			+ <trans>SSH keys</trans>
12			+ </entry>
13			+ <entry>
14			+ <base>FORM_TITLE</base>
15			+ <trans>Change user remote access settings</trans>
16			+ </entry>
17			+ <entry>
18			+ <base>SHELL_ACCESS</base>
19			+ <trans>Shell</trans>
20			+ </entry>
21			+ <entry>
22			+ <base>SUDO</base>
23			+ <trans>Sudo</trans>
24			+ </entry>
25			+ <entry>
26			+ <base>SSH_KEYS</base>
27			+ <trans>SSH Keys</trans>
28			+ </entry>
29			+ <entry>
30			+ <base>CHROOT_PATH</base>
31			+ <trans>Chroot Path</trans>
32			+ </entry>
33			+ <entry>
34			+ <base>CHROOT_PATH_NOT_GIVEN</base>
35			+ <trans>Chroot Path not given</trans>
36			+ </entry>
37			+ <entry>
38			+ <base>CHROOT_PATH_NON_EXISTANT</base>
39			+ <trans>Chroot Path does not exist</trans>
40			+ </entry>
41			+ <entry>
42			+ <base>SELECT_CHROOT_PATH</base>
43			+ <trans>Select Chroot Path</trans>
44			+ </entry>
45			+ <entry>
46			+ <base>VPN_ACCESS</base>
47			+ <trans>RSSH + VPN Access</trans>
48			+ </entry>
49			+ <entry>
50			+ <base>SHELL_ACCESS</base>
51			+ <trans>Shell Access</trans>
52			+ </entry>
53			+ <entry>
54			+ <base>SUDOER_ACCESS</base>
55			+ <trans>Sudo Access</trans>
56			+ </entry>
57			+ <entry>
58			+ <base>MODIFY_DESCRIPTION</base>
59			+ <trans><![CDATA[ <p> Enabling bash shell access for a user account poses a security risk. Only use this option if you know what you are doing. A safer option is to allow rssh access (sftp, ssh & rsync). </p> <p> Sudo access allows users to execute commands with the permissions of the root account without knowing the root password. This is more desirable than passing around the root password. Setting Sudo to yes also sets the shell to bash </p> <p> SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened. </p> <p> Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field. </p> <p> Enter the public SSH Keys to allow ssh access without passwords, keys should be pasted as a single line, but they will wrap onto three or more lines in the display. To delete all keys type "deletekeys". </p> ]]></trans>
60			+ </entry>
61			+ <entry>
62			+ <base>SSHKEYS_DESCRIPTION</base>
63			+ <trans>Enter the public SSH Keys to allow ssh access without passwords, keys should be pasted as a single line, but they will wrap onto three or more lines in the display. To delete all keys type "deletekeys".</trans>
64			+ </entry>
65			+</lexicon>