diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e594810 --- /dev/null +++ b/.gitignore @@ -0,0 +1,4 @@ +*.rpm +*.log +*spec-20* +*.tar.xz diff --git a/Makefile b/Makefile new file mode 100644 index 0000000..e189c41 --- /dev/null +++ b/Makefile @@ -0,0 +1,21 @@ +# Makefile for source rpm: smeserver-remoteuseraccess +# $Id: Makefile,v 1.1 2020/10/26 14:56:47 brianr Exp $ +NAME := smeserver-remoteuseraccess +SPECFILE = $(firstword $(wildcard *.spec)) + +define find-makefile-common +for d in common ../common ../../common ; do if [ -f $$d/Makefile.common ] ; then if [ -f $$d/CVS/Root -a -w $$/Makefile.common ] ; then cd $$d ; cvs -Q update ; fi ; echo "$$d/Makefile.common" ; break ; fi ; done +endef + +MAKEFILE_COMMON := $(shell $(find-makefile-common)) + +ifeq ($(MAKEFILE_COMMON),) +# attept a checkout +define checkout-makefile-common +test -f CVS/Root && { cvs -Q -d $$(cat CVS/Root) checkout common && echo "common/Makefile.common" ; } || { echo "ERROR: I can't figure out how to checkout the 'common' module." ; exit -1 ; } >&2 +endef + +MAKEFILE_COMMON := $(shell $(checkout-makefile-common)) +endif + +include $(MAKEFILE_COMMON) diff --git a/README.md b/README.md index 122ce36..4c6a5c9 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,15 @@ -# smeserver-remoteuseraccess +# smeserver-remoteuseraccess -SMEServer Koozali developed git repo for smeserver-remoteuseraccess smecontribs \ No newline at end of file +SMEServer Koozali developed git repo for smeserver-remoteuseraccess smecontribs + +## Wiki +
https://wiki.koozali.org/Remoteuseraccess + +## Bugzilla +Show list of outstanding bugs: [here](https://bugs.koozali.org/buglist.cgi?component=smeserver-remoteuseraccess&product=SME%20Contribs&query_format=advanced&limit=0&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=CONFIRMED) + +## Description + +
*This description has been generated by an LLM AI system and cannot be relied on to be fully correct.* +*Once it has been checked, then this comment will be deleted* +
diff --git a/additional/COPYING b/additional/COPYING new file mode 100644 index 0000000..196760e --- /dev/null +++ b/additional/COPYING @@ -0,0 +1,340 @@ + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc. + 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Library General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) 19yy + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA + + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) 19yy name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Library General +Public License instead of this License. diff --git a/contriborbase b/contriborbase new file mode 100644 index 0000000..9b7fd51 --- /dev/null +++ b/contriborbase @@ -0,0 +1 @@ +contribs10 diff --git a/createlinks b/createlinks new file mode 100644 index 0000000..e3217e6 --- /dev/null +++ b/createlinks @@ -0,0 +1,10 @@ +#!/usr/bin/perl -w +use esmith::Build::CreateLinks qw(:all); + +panel_link("remoteuseraccess", 'manager'); + +foreach $event (qw( create delete modify )) +{ +templates2events("/etc/proftpd.conf", "user-${event}"); +templates2events("/etc/sudoers", "user-${event}"); +} diff --git a/root/etc/e-smith/events/actions/conf-shell b/root/etc/e-smith/events/actions/conf-shell new file mode 100644 index 0000000..0f591fe --- /dev/null +++ b/root/etc/e-smith/events/actions/conf-shell @@ -0,0 +1,56 @@ +#!/usr/bin/perl -w + +package esmith; + +use strict; +use Errno; +use esmith::config; +use esmith::util; + +my %conf; +tie %conf, 'esmith::config'; + +my %accounts; +tie %accounts, 'esmith::config', '/home/e-smith/db/accounts'; + +my $event = $ARGV [0]; +my $userName = $ARGV [1]; + +die "Username argument missing." unless defined ($userName); + +my $value = $accounts {$userName}; +my ($type, %properties) = split (/\|/, $value, -1); + +if ($type ne 'user') +{ + die "Account $userName is not a user account; modify user failed.\n"; +} + +# defaults to rssh with no rights +my $Shell=$properties{'Shell'} || 'rssh'; + +if (($Shell eq 'bash') || ($Shell eq 'sudo')) +{ + $Shell = '/bin/bash'; +} +else +{ + $Shell = '/usr/bin/rssh'; +} + +my $cmd = "/usr/sbin/usermod"; +$cmd .= " -s \"$Shell\""; +$cmd .= " '$userName'"; + +my $discard = `$cmd`; +if ($? != 0) +{ + die "Failed to modify account $userName.\n"; +} + +esmith::util::processTemplate (\%conf, "/etc/sudoers"); +chmod 0440, "/etc/sudoers"; + +esmith::util::processTemplate (\%conf, "/etc/rssh.conf"); + +esmith::util::processTemplate (\%conf, "/etc/proftpd.conf"); diff --git a/root/etc/e-smith/events/smeserver-remoteuseraccess-update/.gitignore b/root/etc/e-smith/events/smeserver-remoteuseraccess-update/.gitignore new file mode 100644 index 0000000..e69de29 diff --git a/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..19257cb --- /dev/null +++ b/root/etc/e-smith/locale/bg/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Отдалечен достъп на потребителите + + + SSH keys + SSH ключове + + + FORM_TITLE + Промяна на параметрите за отдалечен достъп на потребител + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH ключове + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Пътят за Chroot не е зададен + + + CHROOT_PATH_NON_EXISTANT + Пътят за Chroot не съществува + + + SELECT_CHROOT_PATH + Изберете път за Chroot + + + VPN_ACCESS + RSSH + VPN достъп + + + SHELL_ACCESS + Shell достъп + + + SUDOER_ACCESS + Sudo достъп + + + MODIFY_DESCRIPTION + Включването на достъпа до bash shell за потребител създава риск за сигурността. Използвайте тази възможност ако знаете какво правите. По-сигурна възможност е да позволите достъп до rssh (sftp, ssh & rsync).

Достъпът до Sudo позволява на потребителите да изпълняват команди с правата на root account без да знаят неговата парола. Това е за предпочитане, пред предоставянето на паролата ма root. Задаването на Sudo на "да" също задава shell на bash

Достъпът до SHELL, VPN & FTP за потребители зависи от това дали достъпа е даден в настройките в панела за отдалечен достъп.

Изберете FTP Chroot път от падащия списък или го въведете в текстовото поле, изборът от падащия списък ще промени текстовото поле.

Въведете публичните SSH ключове за да позволите ssh достъп без пароли, ключовете трябва да се поставят като един ред, но той ще бъде пренесен на три или повече реда на екрана. За да изтриете всички ключове напишете "deletekeys".

]]> + + + SSHKEYS_DESCRIPTION + Въведете публичните SSH ключове за да позволите ssh достъп без пароли, ключовете трябва да се поставят като един ред, но той ще бъде пренесен на три или повече реда на екрана. За да изтриете всички ключове напишете "deletekeys". + + diff --git a/root/etc/e-smith/locale/da/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/da/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..5c7d9b5 --- /dev/null +++ b/root/etc/e-smith/locale/da/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Bruger Fjernadgang + + + SSH keys + SSH nøgler + + + FORM_TITLE + Skift indstillinger for fjernadgang + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH nøgle + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path er ikke angivet + + + CHROOT_PATH_NON_EXISTANT + Chroot Path eksisterer ikke + + + SELECT_CHROOT_PATH + Vælg Chroot Path + + + VPN_ACCESS + RSSH + VPN adgang + + + SHELL_ACCESS + Shell adgang + + + SUDOER_ACCESS + Sudo adgang + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Indtast den offentlige SSH nøgle for at tillade adgang uden kodeord, nøgler skal indsættes som en enkelt linje, men vil blive ombrudt til tre eller flere linjer på skærmen. Skriv "deletekeys" For at slette alle nøgler. + + diff --git a/root/etc/e-smith/locale/de/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/de/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..053f1b1 --- /dev/null +++ b/root/etc/e-smith/locale/de/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Benutzer-Fernzugriff + + + SSH keys + SSH Schlüssel + + + FORM_TITLE + Online-Handbuch ]]> + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Schlüssel + + + CHROOT_PATH + Chroot Pfad + + + CHROOT_PATH_NOT_GIVEN + Nein Chroot Pfad + + + CHROOT_PATH_NON_EXISTANT + Chroot Pfad Falscher + + + SELECT_CHROOT_PATH + Chroot Pfad auswählen + + + VPN_ACCESS + VPN Zugang + + + SHELL_ACCESS + Shell Zugang + + + SUDOER_ACCESS + Sudo Zugang + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Für den SSH-Zugang ohne Kennwort geben Sie bitte den öffentlichen SSH-Schlüssel ein. Der Schlüssel sollte als ganze Zeile kopiert und eingefügt werden, erscheint dann allerdings auf dem Bildschirm in 3 Zeilen. Um den Schlüssel zu löschen, geben Sie "deletekeys" ein. + + diff --git a/root/etc/e-smith/locale/el/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/el/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..fa81058 --- /dev/null +++ b/root/etc/e-smith/locale/el/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Χρήστες Απομεμακρυσμένης Πρόσβασης + + + SSH keys + Κλείδες SSH + + + FORM_TITLE + Αλλαγή ρυθμίσεων χρηστών με δικαίωμα απομεμακρυσμένης πρόσβασης + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Κλείδες SSH + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Δεν δόθηκε Chroot Path + + + CHROOT_PATH_NON_EXISTANT + Δεν υφίσταται το παραπάνω Chroot Path + + + SELECT_CHROOT_PATH + Επιλογή Chroot Path + + + VPN_ACCESS + Πρόσβαση RSSH + VPN + + + SHELL_ACCESS + Πρόσβαση Κελύφους (Shell) + + + SUDOER_ACCESS + Πρόσβαση Sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Εισάγετε τις δημόσιες Κλείδες SSH για να επιτρέψετε πρόσβαση ssh χωρίς κωδικούς, η επικόλληση των κλειδών θα πρέπει να γίνει σε μία γραμμή, αλλά θα αναδιπλωθούν σε τρεις ή περισσότερες γραμμές στην οθόνη. Για να διαγράψετε όλες τις κλείδες πληκτρολογήστε "deletekeys". + + diff --git a/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..1c9bea8 --- /dev/null +++ b/root/etc/e-smith/locale/en-us/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,91 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + + 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). +

+

+ 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 +

+

+ SHELL, VPN & FTP access for users depend on the + settings in the Remote Access Panel being opened. +

+

+ Select an FTP Chroot path from the drop down box or enter it in the text field, + the selection will overwrite the text field. +

+

+ 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". +

+ ]]> + + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/es/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/es/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..04eb522 --- /dev/null +++ b/root/etc/e-smith/locale/es/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Acceso de Usuario Remoto + + + SSH keys + Claves SSH + + + FORM_TITLE + Cambiar preferencias del acceso de usuario remoto + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Claves SSH + + + CHROOT_PATH + Ruta Chroot + + + CHROOT_PATH_NOT_GIVEN + No ha proporcionado la ruta chroot + + + CHROOT_PATH_NON_EXISTANT + Ruta chroot no existe + + + SELECT_CHROOT_PATH + Seleccionar Ruta Chroot + + + VPN_ACCESS + Acceso RSSH y VPN + + + SHELL_ACCESS + Acceso Shell + + + SUDOER_ACCESS + Acceso sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Introduzca la clave publica SSH para permitir el acceso ssh sin clave. Necesita introducir la clave SSH en una sola linea, pero va a aparecer en múltiples lineas. Para borrar todas las claves, teclee "deletekeys". + + diff --git a/root/etc/e-smith/locale/et/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/et/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..6336351 --- /dev/null +++ b/root/etc/e-smith/locale/et/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Kasutajate kaugahalduse juurdepääs + + + SSH keys + SSH keys + + + FORM_TITLE + Muuda kasutajate kaughalduse juurdepääsu seadeid + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path pole määratud + + + CHROOT_PATH_NON_EXISTANT + Chroot Path pole olemas + + + SELECT_CHROOT_PATH + Vali Chroot Path + + + VPN_ACCESS + RSSH + VPN juurdepääs + + + SHELL_ACCESS + Shell juurdepääs + + + SUDOER_ACCESS + Sudo juurdepääs + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..e232ca6 --- /dev/null +++ b/root/etc/e-smith/locale/fr/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Accès à distance Utilisateur + + + SSH keys + Clés SSH + + + FORM_TITLE + Modifier les paramètres d'accès à distance des utilisateurs + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Clés SSH + + + CHROOT_PATH + Chemin Chroot + + + CHROOT_PATH_NOT_GIVEN + Chemin Chroot non défini + + + CHROOT_PATH_NON_EXISTANT + Le chemin Chroot n'existe pas + + + SELECT_CHROOT_PATH + Sélectionnez le chemin Chroot + + + VPN_ACCESS + VPN + Accès RSSH + + + SHELL_ACCESS + Accès au Shell + + + SUDOER_ACCESS + Accès Sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Entrez les clés publiques SSH Keys pour autoriser l'accès ssh sans mot de passe, chaque clé devant être collée sur une seule ligne (l'affichage sera tronqué sur 3 lignes ou plus). Pour supprimer toutes les clés, tapez "deletekeys". + + diff --git a/root/etc/e-smith/locale/he/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/he/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..0f77eaa --- /dev/null +++ b/root/etc/e-smith/locale/he/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..67b0505 --- /dev/null +++ b/root/etc/e-smith/locale/hu/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + (1) Parancsértelmező (2) Héj + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/id/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/id/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..12f7a90 --- /dev/null +++ b/root/etc/e-smith/locale/id/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/it/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/it/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..949dcf7 --- /dev/null +++ b/root/etc/e-smith/locale/it/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Accesso Remoto Utente + + + SSH keys + Chiavi SSH + + + FORM_TITLE + Modifica impostazioni di accesso remoto dell'utente + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Chiavi SSH + + + CHROOT_PATH + Percorso Chroot + + + CHROOT_PATH_NOT_GIVEN + Percorso Chroot non definito + + + CHROOT_PATH_NON_EXISTANT + Percorso Chroot inesistente + + + SELECT_CHROOT_PATH + Selezionare il percorso Chroot + + + VPN_ACCESS + Accesso RSSH + VPN + + + SHELL_ACCESS + Accesso Shell + + + SUDOER_ACCESS + Accesso Sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Inserire la chiave SSH pubblica per consentire l'accesso pubblico senza password; la chiave deve essere incollata come una riga unica ma verrà divisa in tre o più righe a video. Per cancellare tutte le chiavi digitare "deletekeys". + + diff --git a/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..1ff7b8b --- /dev/null +++ b/root/etc/e-smith/locale/ja/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + シェル + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..6ef426c --- /dev/null +++ b/root/etc/e-smith/locale/nb/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Stav + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..2270740 --- /dev/null +++ b/root/etc/e-smith/locale/nl/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Toegang voor gebruiker op afstand + + + SSH keys + SSH sleutels + + + FORM_TITLE + Verander instellingen voor gebruiker op afstand + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH sleutels + + + CHROOT_PATH + Chroot Pad + + + CHROOT_PATH_NOT_GIVEN + Chroot Pad niet opgegeven + + + CHROOT_PATH_NON_EXISTANT + Chroot Pad bestaat niet + + + SELECT_CHROOT_PATH + Kies Chroot Pad + + + VPN_ACCESS + RSSH + VPN toegang + + + SHELL_ACCESS + Shell Toegang + + + SUDOER_ACCESS + Sudo Toegang + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Geef de publieke SSH sleutels op om toegang voor ssh toe te staan zonder wachtwoord, sleutels moeten worden geplakt als één enkele regel maar zullen worden verspreid over die of meer regels in het scherm. Om alle sleutels te verwijderen, type dan \"deletekeys\". + + diff --git a/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..b797eb7 --- /dev/null +++ b/root/etc/e-smith/locale/pl/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Powłoka + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..e5a1ada --- /dev/null +++ b/root/etc/e-smith/locale/pt-br/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Acesso Remoto do Usuário + + + SSH keys + Chaves SSH + + + FORM_TITLE + Mudar configurações de acesso remoto do usuário + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Chaves SSH + + + CHROOT_PATH + Caminho do CHROOT + + + CHROOT_PATH_NOT_GIVEN + Caminho do CHROOT não fornecido + + + CHROOT_PATH_NON_EXISTANT + Caminho do CHROOT não existe + + + SELECT_CHROOT_PATH + Selecione o caminho do CHROOT + + + VPN_ACCESS + Acesso RSSH e VPN + + + SHELL_ACCESS + Acesso Shell + + + SUDOER_ACCESS + Acesso Sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Entre as chave de SSH públicas para permitir acesso SSH sem senhas, as chaves devem ser coladas como uma linha simples mas serão quebradas em três ou mais linhas para exibição na tela. Para apagar todas as chaves escreva "deletekeys". + + diff --git a/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..6846057 --- /dev/null +++ b/root/etc/e-smith/locale/pt/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Acesso Remoto do Usuário + + + SSH keys + Chaves SSH + + + FORM_TITLE + Mudar configurações de acesso remoto do usuário + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + Chaves SSH + + + CHROOT_PATH + Caminho do CHROOT + + + CHROOT_PATH_NOT_GIVEN + Caminho do CHROOT não fornecido + + + CHROOT_PATH_NON_EXISTANT + Caminho do CHROOT não existe + + + SELECT_CHROOT_PATH + Selecione o caminho do CHROOT + + + VPN_ACCESS + Acesso RSSH e VPN + + + SHELL_ACCESS + Acesso Shell + + + SUDOER_ACCESS + Acesso Sudo + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Entre as chave de SSH públicas para permitir acesso SSH sem senhas, as chaves devem ser coladas como uma linha simples mas serão quebradas em três ou mais linhas para exibição na tela. Para apagar todas as chaves escreva "deletekeys". + + diff --git a/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..3fcfaf3 --- /dev/null +++ b/root/etc/e-smith/locale/ro/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..a2fb92f --- /dev/null +++ b/root/etc/e-smith/locale/ru/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Пользователь удаленного доступа + + + SSH keys + SSH ключи + + + FORM_TITLE + Изменение параметров удаленного доступа пользователя + + + SHELL_ACCESS + Оболочка + + + SUDO + Sudo + + + SSH_KEYS + SSH ключи + + + CHROOT_PATH + Chroot путь + + + CHROOT_PATH_NOT_GIVEN + Chroot путь не задан + + + CHROOT_PATH_NON_EXISTANT + Chroot путь не существует + + + SELECT_CHROOT_PATH + Выберите Chroot путь + + + VPN_ACCESS + RSSH + VPN допступ + + + SHELL_ACCESS + Shell доступ + + + SUDOER_ACCESS + Sudo доступ + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..33e34a3 --- /dev/null +++ b/root/etc/e-smith/locale/sl/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..5b8617e --- /dev/null +++ b/root/etc/e-smith/locale/sv/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + Användares fjärråtkomst + + + SSH keys + SSH-nycklar + + + FORM_TITLE + Ändra inställningar för användares fjärråtkomst + + + SHELL_ACCESS + Skal + + + SUDO + Sudo + + + SSH_KEYS + SSH-nycklar + + + CHROOT_PATH + Chroot-sökväg + + + CHROOT_PATH_NOT_GIVEN + Chroot-sökväg inte angiven + + + CHROOT_PATH_NON_EXISTANT + Chroot-sökväg existerar inte + + + SELECT_CHROOT_PATH + Välj Chroot-sökväg + + + VPN_ACCESS + RSSH + VPN-åtkomst + + + SHELL_ACCESS + Skalåtkomst + + + SUDOER_ACCESS + Sudo-åtkomst + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + Ange de publika SSH-nycklarna som tillåter ssh-åtkomst utan lösenord. Nycklarna skall klistras in som en rad, men de presenteras på 3 eller fler rader i rutan. För att radera samtliga nycklar skriv "deletekeys". + + diff --git a/root/etc/e-smith/locale/th/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/th/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..aba2ea6 --- /dev/null +++ b/root/etc/e-smith/locale/th/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell, เชลล์ + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..ac9733b --- /dev/null +++ b/root/etc/e-smith/locale/tr/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + User Remote Access + + + SSH keys + SSH keys + + + FORM_TITLE + Change user remote access settings + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH Keys + + + CHROOT_PATH + Chroot Path + + + CHROOT_PATH_NOT_GIVEN + Chroot Path not given + + + CHROOT_PATH_NON_EXISTANT + Chroot Path does not exist + + + SELECT_CHROOT_PATH + Select Chroot Path + + + VPN_ACCESS + RSSH + VPN Access + + + SHELL_ACCESS + Shell Access + + + SUDOER_ACCESS + Sudo Access + + + MODIFY_DESCRIPTION + 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).

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

SHELL, VPN & FTP access for users depend on the settings in the Remote Access Panel being opened.

Select an FTP Chroot path from the drop down box or enter it in the text field, the selection will overwrite the text field.

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".

]]> + + + SSHKEYS_DESCRIPTION + 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". + + diff --git a/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..e58e99d --- /dev/null +++ b/root/etc/e-smith/locale/zh-cn/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + 用户远程访问 + + + SSH keys + SSH 密钥 + + + FORM_TITLE + 修改用户远程访问设置 + + + SHELL_ACCESS + Shell + + + SUDO + Sudo + + + SSH_KEYS + SSH 密钥 + + + CHROOT_PATH + Chroot 路径 + + + CHROOT_PATH_NOT_GIVEN + Chroot 路径未设置 + + + CHROOT_PATH_NON_EXISTANT + Chroot 路径不存在 + + + SELECT_CHROOT_PATH + 选择 Chroot 路径 + + + VPN_ACCESS + RSSH + VPN 访问 + + + SHELL_ACCESS + Shell 访问 + + + SUDOER_ACCESS + Sudo 访问 + + + MODIFY_DESCRIPTION + 启用 bash shell 访问用户账户存在安全风险。仅仅在您知道后果的情况下使用。 一个更安全的选项是允许RSSH访问(sftp, ssh & rsync)。

Sudo 访问允许用户在不知道root密码的情况下以root权限执行命令。 这比在网络中传输root密码更为可取。启用Sudo也意味着启用 bash shell。

SHELL, VPN & FTP 访问的前提是远程访问面板设置被开启。

在下面的框框或文本区填上一个 FTP Chroot 路径，位置栏会覆盖文本区域。

输入SSH公钥可以允许SSH无需密码访问，密钥每行粘贴一个，但显示时可能会占据三行或更多。要删除所有密钥请输入"deletekeys"。

]]> + + + SSHKEYS_DESCRIPTION + 输入SSH公钥可以允许SSH无需密码访问，密钥每行粘贴一个，但显示时可能会占据三行或更多。要删除所有密钥请输入"deletekeys"。 + + diff --git a/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..11ec50c --- /dev/null +++ b/root/etc/e-smith/locale/zh-tw/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,62 @@ + + + User Remote Access + 使用者遠端存取 + + + SSH keys + SSH金鑰 + + + FORM_TITLE + 改變使用者遠端存取設定 + + + SHELL_ACCESS + 命令列 + + + SUDO + 超級使用者 + + + SSH_KEYS + SSH金鑰 + + + CHROOT_PATH + 置換根目錄的路徑 + + + CHROOT_PATH_NOT_GIVEN + 未給定置換根目錄的路徑 + + + CHROOT_PATH_NON_EXISTANT + 置換根目錄的路徑不存在 + + + SELECT_CHROOT_PATH + 選擇置換根目錄的路徑 + + + VPN_ACCESS + RSSH + VPN存取 + + + SHELL_ACCESS + 命令列存取 + + + SUDOER_ACCESS + 超級使用者存取 + + + MODIFY_DESCRIPTION + 啟用使用者帳號的bash shell存取存在安全風險。僅能在您知道自己在做什麼的情況下使用這個選項。更安全的選擇是允許rssh存取(sftp, ssh & rsync)。

Sudo存取允許使用者執行root帳號權限的命令而無需root密碼。此較傳遞root密碼更為可取。啟用Sudo亦啟用shell為bash。

SHELL, VPN & FTP使用者存取基於遠端存取控制台設定的開啟。

從下拉框或文字輸入區中選擇FTP置換根目錄的路徑，蓋選項將覆寫文字區。

輸入SSH公開金鑰以允許ssh無需密碼存取，金鑰需以無間斷方式一整行貼上，但可能會以三行以上方式顯示。要刪除所有金鑰請輸入"deletekeys"。

]]> + + + SSHKEYS_DESCRIPTION + 輸入SSH金鑰以允許ssh無密碼存取，金鑰需以無間斷方式一整行貼上，但可能會以三行以上方式顯示。要刪除所有金鑰請輸入"deletekeys"。 + + diff --git a/root/etc/e-smith/templates.metadata/etc/sudoers b/root/etc/e-smith/templates.metadata/etc/sudoers new file mode 100644 index 0000000..cf22e96 --- /dev/null +++ b/root/etc/e-smith/templates.metadata/etc/sudoers @@ -0,0 +1 @@ +PERMS=0440 diff --git a/root/etc/e-smith/templates/etc/sudoers/10root b/root/etc/e-smith/templates/etc/sudoers/10root new file mode 100644 index 0000000..b06d941 --- /dev/null +++ b/root/etc/e-smith/templates/etc/sudoers/10root @@ -0,0 +1,3 @@ + +root ALL=(ALL) ALL + diff --git a/root/etc/e-smith/templates/etc/sudoers/20users b/root/etc/e-smith/templates/etc/sudoers/20users new file mode 100644 index 0000000..7f36ad1 --- /dev/null +++ b/root/etc/e-smith/templates/etc/sudoers/20users @@ -0,0 +1,22 @@ +{ + my %accounts; + tie %accounts, 'esmith::config', '/home/e-smith/db/accounts'; + + my $key; + my $value; + my $result = ""; + + while (($key,$value) = each %accounts) + { + my ($type, %properties) = split (/\|/, $value, -1); + if ($type eq 'user') + { + if (defined($properties{'Sudoer'}) && $properties{'Sudoer'} eq 'yes') + { + $result .= "$key ALL=(ALL) ALL\n"; + } + } + } + + $result; +} diff --git a/root/etc/e-smith/web/functions/remoteuseraccess b/root/etc/e-smith/web/functions/remoteuseraccess new file mode 100644 index 0000000..26e2d83 --- /dev/null +++ b/root/etc/e-smith/web/functions/remoteuseraccess @@ -0,0 +1,103 @@ +#!/usr/bin/perl -wT + +#---------------------------------------------------------------------- +# heading : Security +# description : User Remote Access +# navigation : 1000 1250 +# +# Modified (c) 2002,2006 Stephen Noble +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +#---------------------------------------------------------------------- + +use strict; +use warnings; + +use esmith::FormMagick::Panel::remoteuseraccess; + +my $fm = esmith::FormMagick::Panel::remoteuseraccess->new(); +$fm->display(); + +__DATA__ +
+ + + + + + + + + MODIFY_DESCRIPTION + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
diff --git a/root/etc/e-smith/web/functions/userpanel-sshkeys b/root/etc/e-smith/web/functions/userpanel-sshkeys new file mode 100644 index 0000000..d78bf69 --- /dev/null +++ b/root/etc/e-smith/web/functions/userpanel-sshkeys @@ -0,0 +1,62 @@ +#!/usr/bin/perl -wT + +#---------------------------------------------------------------------- +# heading : Your Settings +# description : SSH keys +# longdesc : add public keys to allow ssh access without passwords +# navigation : 100 600 +# +# Modified (c) 2002,2006 Stephen Noble +# +# This program is free software; you can redistribute it and/or modify +# it under the terms of the GNU General Public License as published by +# the Free Software Foundation; either version 2 of the License, or +# (at your option) any later version. +# +# uses the FormMagick Panel for remoteuseraccess +# but pulls username from $ENV{'REMOTE_USER'}; +# rather then being selected from a table +# +#---------------------------------------------------------------------- + +use strict; +use warnings; + +use esmith::FormMagick::Panel::remoteuseraccess; + +my $fm = esmith::FormMagick::Panel::remoteuseraccess->new(); +$fm->display(); + +__DATA__ +
+ + + + SSHKEYS_DESCRIPTION + + + + + + + + + + + + + + + + + + +
diff --git a/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/remoteuseraccess.pm b/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/remoteuseraccess.pm new file mode 100644 index 0000000..ceb0f17 --- /dev/null +++ b/root/usr/share/perl5/vendor_perl/esmith/FormMagick/Panel/remoteuseraccess.pm @@ -0,0 +1,421 @@ +#---------------------------------------------------------------------- +# remoteuseraccess.pm +# support@dungog.net +#---------------------------------------------------------------------- + +package esmith::FormMagick::Panel::remoteuseraccess; + +use strict; +use warnings; + +use esmith::util; +use esmith::FormMagick; +use esmith::AccountsDB; +use esmith::ConfigDB; + +use Exporter; +use Carp qw(verbose); + +use HTML::Tabulate; + +our @ISA = qw(esmith::FormMagick Exporter); + +our @EXPORT = qw(); + +our $db = esmith::ConfigDB->open(); +our $adb = esmith::AccountsDB->open(); + +our $PanelUser = $ENV{'REMOTE_USER'} ||''; +$PanelUser = $1 if ($PanelUser =~ /^([a-z][\-a-z0-9]*)$/); + +sub new { + shift; + my $self = esmith::FormMagick->new(); + $self->{calling_package} = (caller)[0]; + bless $self; + return $self; +} + +#server-manager functions +sub user_accounts_exist +{ + return scalar $adb->users; +} + +sub print_table +{ + my $self = shift; + my $q = $self->{cgi}; + + my $user_table = + { + title => $self->localise('USER_LIST_CURRENT'), + + stripe => '#D4D0C8', + + fields => [ qw(User FullName shell sudo keys chroot vpn Modify) ], + + labels => 1, + + field_attr => { + User => { + label_escape => 0, + label => $self->localise('ACCOUNT') + }, + FullName => { + label_escape => 0, + label => $self->localise('USER_NAME') + }, + shell => { + label_escape => 0, + label => $self->localise('SHELL_ACCESS') + }, + sudo => { + label_escape => 0, + label => $self->localise('SUDO') + }, + keys => { + label_escape => 0, + label => $self->localise('SSH_KEYS') + }, + chroot => { + label_escape => 0, + label => $self->localise('CHROOT_PATH') + }, + vpn => { + label_escape => 0, + label => $self->localise('VPN_ACCESS') + }, + Modify => { + label_escape => 0, + label => $self->localise('MODIFY'), + link => \&modify_link + }, + } + }; + + my @data = (); + my @users = $adb->users; + + return $self->localise("ACCOUNT_USER_NONE") if (@users == 0); + + for my $user (@users) + { + my $username = $user->key; + # make clearer by only showing yes and localise + my $vpn = $user->prop('VPNClientAccess') || ''; + if ($vpn eq 'yes') { $vpn = 'YES'; } else { $vpn = ''; } + my $sudo = $user->prop('Sudoer') || ''; + if ($sudo eq 'yes') { $sudo = 'YES'; } else { $sudo = ''; } + my $keys = ''; + my $file = "/home/e-smith/files/users/$username/.ssh/authorized_keys2"; + if (( -e $file ) && (! -z $file )) + { $keys = 'YES'; } + + my $shell = $user->prop('Shell') || ''; + if ($shell eq '/usr/bin/rssh') { $shell = ''; } + + my $ChrootDir = $user->prop('ChrootDir') || ""; + $ChrootDir =~ s:/home/e-smith/files/ibays/::; + $ChrootDir =~ s:/home/e-smith/files/users/$username/home:home:; + + push @data, + { User => $user->key, + FullName => $user->prop('FirstName') . " " . + $user->prop('LastName'), + Sudoer => $user->prop('Sudoer') || 'no', + VPNClientAccess => $user->prop('VPNClientAccess') || 'no', + shell => $shell, + chroot => $ChrootDir, + ChrootDir => $user->prop('ChrootDir') || "/home/e-smith/files/users/$username/home", + sudo => $self->localise($sudo), + keys => $self->localise($keys), + vpn => $self->localise($vpn), + Modify => $self->localise('MODIFY'), + } + } + + my $t = HTML::Tabulate->new($user_table); + + $t->render(\@data, $user_table); +} + +sub modify_link +{ + my ($data_item, $row, $field) = @_; + + return "remoteuseraccess?" . + join("&", + "page=0", + "page_stack=", + "Next=Next", + "User=" . $row->{User}, + "FullName=" . $row->{FullName}, + "Sudoer=" . $row->{Sudoer}, + "Shell=" . $row->{shell}, + "ChrootDir=" . $row->{ChrootDir}, + "VPNClientAccess=" . $row->{VPNClientAccess}, + "wherenext=PAGE_MODIFY"); +} + +sub get_chroot_dir +{ + my $self = shift; + my %existingAccounts = ('' => '', + 'home' => ". ~/home" , + '/home/e-smith/files'=> '.. /home/e-smith/files' ); + + foreach my $account ($adb->get_all) + { + if ($account->prop('type') =~ /(ibay)/) + { + $existingAccounts{"/home/e-smith/files/ibays/" . $account->key} = $account->key; + $existingAccounts{"/home/e-smith/files/ibays/" . $account->key . "/html"} = $account->key . "/html"; + $existingAccounts{"/home/e-smith/files/ibays/" . $account->key . "/files"} = $account->key. "/files"; + } + } + + return(\%existingAccounts); +} + +sub get_keys_text +{ + my $self = shift; + my $q = $self->{cgi}; + + my $user = $q->param('User'); + + my $file = "/home/e-smith/files/users/$user/.ssh/authorized_keys2"; + + my $sshKeys = ''; + # if exists and is not empty + if (( -e $file ) && (! -z $file )) + { + open (SSHKEY, "<$file") + or die "Error: Could not open file: $file\n"; + my @sshTemp = ; + $sshKeys = join ("", @sshTemp); + + close SSHKEY; + } + + return $sshKeys; +} + +sub change_settings +{ + my $self = shift; + my $q = $self->{cgi}; + my $Shell = $q->param ('Shell'); + my $Sudoer = $q->param ('Sudoer'); + my $VPNClientAccess = $q->param ('VPNClientAccess'); + my $ChrootDir = $q->param ('ChrootDir'); + my $ChrootDir2 = $q->param ('ChrootDir2'); + + my $user = $q->param('User'); + + if ($user =~ /^([a-z][\-a-z0-9]*)$/) + { + $user = $1; + } + + my $sshKeys = $q->param ('sshKeys'); + if ($sshKeys ne '') + { + my $file = "/home/e-smith/files/users/$user/.ssh/authorized_keys2"; + my $dir = "/home/e-smith/files/users/$user/.ssh"; + + # delete .ssh/authorized_keys2 + if ($sshKeys =~ /deletekeys/) + { + system ("/bin/rm -rf $file") == 0 + or die ("Error deleting $file.\n"); + } + else + { + # Strip out DOS Carriage Returns (CR) + $sshKeys =~ s/\r//g; + + unless ( -e $file ) + { system ("/bin/mkdir -p $dir") == 0 + or die ("Error creating ssh directory.\n"); } + + unlink $file; + + open (SSHKEY, ">$file") + or die ("Error saving SSH Keys.\n"); + + print SSHKEY "$sshKeys\n"; + close SSHKEY; + + system ("/bin/chown -R $user.$user $dir") == 0 + or die ("Error chown .ssh directory.\n"); + } + } + + # if the drop down is blank and field is valid + # set the field to the drop down, save the drop down + if (($ChrootDir2 eq '' ) && ($ChrootDir ne '')) + { + $ChrootDir2 = $ChrootDir || ''; + } + + if (($Sudoer eq 'yes') or ($Shell eq '/bin/bash')) + { + $adb->set_prop($user, 'Shell', '/bin/bash'); + } else { + $adb->set_prop($user, 'Shell', '/usr/bin/rssh'); + } + + $adb->set_prop($user, 'Sudoer', $Sudoer); + $adb->set_prop($user, 'ChrootDir', $ChrootDir2); + $adb->set_prop($user, 'VPNClientAccess', $VPNClientAccess); + + system ("/sbin/e-smith/signal-event", "user-modify", $user) == 0 + or die ("Error occurred updating user access\n"); + + return $self->success("SUCCESS"); +} + +#userpanel functions +sub get_panel_user +{ + return $PanelUser; +} + +sub get_full_name +{ + return $adb->get_prop($PanelUser, "FirstName") . " " . + $adb->get_prop($PanelUser, "LastName"); +} + +sub userpanel_keys_text +{ + my $self = shift; + my $q = $self->{cgi}; + + my $file = "/home/e-smith/files/users/$PanelUser/.ssh/authorized_keys2"; + + if ($PanelUser eq 'admin') + { $file = "/root/.ssh/authorized_keys2"; } + + my $sshKeys = ''; + # if exists and is not empty + if (( -e $file ) && (! -z $file )) + { + open (SSHKEY, "<$file") + or die "Error: Could not open file: $file\n"; + my @sshTemp = ; + $sshKeys = join ("", @sshTemp); + + close SSHKEY; + } + + return $sshKeys; +} + +sub userpanel_change_settings +{ + my $self = shift; + my $q = $self->{cgi}; + my $Shell = $q->param ('Shell'); + my $Sudoer = $q->param ('Sudoer'); + my $VPNClientAccess = $q->param ('VPNClientAccess'); + my $ChrootDir = $q->param ('ChrootDir'); + my $ChrootDir2 = $q->param ('ChrootDir2'); + + my $user = $PanelUser; + + if ($user =~ /^([a-z][\-a-z0-9]*)$/) + { + $user = $1; + } + + my $sshKeys = $q->param ('sshKeys'); + if ($sshKeys ne '') + { + my $file = "/home/e-smith/files/users/$user/.ssh/authorized_keys2"; + my $dir = "/home/e-smith/files/users/$user/.ssh"; + if ($user eq 'admin') + { $file = "/root/.ssh/authorized_keys2"; + $dir = "/root/.ssh"; } + + # delete .ssh/authorized_keys2 + if ($sshKeys =~ /deletekeys/) + { + system ("/bin/rm -rf $file") == 0 + or die ("Error deleting $file.\n"); + } + else + { + # Strip out DOS Carriage Returns (CR) + $sshKeys =~ s/\r//g; + + unless ( -e $file ) + { system ("/bin/mkdir -p $dir") == 0 + or die ("Error creating ssh directory.\n"); } + + unlink $file; + + open (SSHKEY, ">$file") + or die ("Error saving SSH Keys.\n"); + + print SSHKEY "$sshKeys\n"; + close SSHKEY; + + system ("/bin/chown -R $user.$user $dir") == 0 + or die ("Error chown .ssh directory.\n"); + } + } + + # if the drop down is blank and field is valid + # set the field to the drop down, save the drop down + if (($ChrootDir2 eq '' ) && ($ChrootDir ne '')) + { + $ChrootDir2 = $ChrootDir || ''; + } + + if (($Sudoer eq 'yes') or ($Shell eq '/bin/bash')) + { + $adb->set_prop($user, 'Shell', '/bin/bash'); + } else { + $adb->set_prop($user, 'Shell', '/usr/bin/rssh'); + } + + $adb->set_prop($user, 'Sudoer', $Sudoer); + $adb->set_prop($user, 'ChrootDir', $ChrootDir2); + $adb->set_prop($user, 'VPNClientAccess', $VPNClientAccess); + + system ("/sbin/e-smith/signal-event", "user-modify", $user) == 0 + or die ("Error occurred updating user access\n"); + + return $self->success("SUCCESS"); +} + +sub CheckChrootDirExists +{ + my $self = shift; + my $q = $self->{cgi}; + + my $ChrootDir = $q->param ('ChrootDir') || ''; + my $ChrootDir2 = $q->param ('ChrootDir2') || ''; + + if ($ChrootDir2 eq '') + { + if ($ChrootDir eq '') + { + return "CHROOT_PATH_NOT_GIVEN"; + } + else + { + if ((-e $ChrootDir ) || ($ChrootDir eq 'home')) + { return "OK"; } + else + { return "CHROOT_PATH_NON_EXISTANT"; } + } + } + else + { return "OK"; } +} + +1; diff --git a/smeserver-remoteuseraccess.spec b/smeserver-remoteuseraccess.spec new file mode 100644 index 0000000..4663a62 --- /dev/null +++ b/smeserver-remoteuseraccess.spec @@ -0,0 +1,284 @@ +# $Id: smeserver-remoteuseraccess.spec,v 1.5 2021/08/23 07:42:21 terryfage Exp $ +# Authority: dungog +# Name: Stephen Noble + +Summary: Smeserver module to configure Shell and FTP access for individual users +%define name smeserver-remoteuseraccess +Name: %{name} +%define version 1.3 +%define release 7 +Version: %{version} +Release: %{release}%{?dist} +License: GNU GPL version 2 +URL: http://www.dungog.net/sme +Group: Networking/Daemons +Source: %{name}-%{version}.tar.xz + +BuildRoot: /var/tmp/e-smith-buildroot +BuildRequires: e-smith-devtools +BuildArchitectures: noarch +Requires: e-smith-release >= 7 +Requires: e-smith-proftpd >= 1.12.0-6 +Requires: e-smith-openssh >= 1.11.0-24 +Requires: e-smith-formmagick >= 1.4.0-12 +Obsoletes: dungog-proftpd-chroot +Obsoletes: e-smith-usershellaccess +Obsoletes: smeserver-sshkeys +AutoReqProv: no + +%description +SME server enhancement to provide a server-manager panel under security +where you can enable shell access on a user by user basis. + +Shells available bash, optionally with sudo +or rssh which allows scp sftp rsync cvs rdist +TODO Chroot RSSH shell access. + +Also sets Chroots FTP access, VPN Client Access, +and allows you to enter ssh keys + +%changelog +* Sat Sep 07 2024 cvs2git.sh aka Brian Read 1.3-7.sme +- Roll up patches and move to git repo [SME: 12338] + +* Sat Sep 07 2024 BogusDateBot +- Eliminated rpmbuild "bogus date" warnings due to inconsistent weekday, + by assuming the date is correct and changing the weekday. + Sat Mar 07 2008 --> Sat Mar 01 2008 or Fri Mar 07 2008 or Sat Mar 08 2008 or .... + Thu May 21 2008 --> Thu May 15 2008 or Wed May 21 2008 or Thu May 22 2008 or .... + +* Mon Aug 23 2021 Terry Fage 1.3-6.sme +- apply locale 2021-08-23 patch + +* Wed Feb 24 2021 Jean-Philipe Pialasse 1.3-5.sme +- fix encoding issue in table display [SME: 11396] + +* Wed Feb 24 2021 Jean-Philipe Pialasse 1.3-4.sme +- add empty -update event [SME: 11056] + +* Mon Oct 26 2020 Brian Read 1.3-3.sme +- Initial import to SME10 tree [SME: 11056] + +* Wed Mar 09 2016 JP Pialasse 1.3-2.sme +- apply locale 2016-03-09 patch + +* Tue Nov 12 2013 Daniel Berteaud 1.3-1.sme +- Rebuild for SME9 + +* Sun Jul 14 2013 JP Pialasse 1.2-38.sme +- apply locale 2013-07-14 patch + +* Sun Mar 06 2011 SME Translation Server 1.2-37.sme +- apply locale 2011-03-06 patch + +* Tue Mar 02 2010 SME Translation Server 1.2-36.sme +- apply locale 2010-03-02 patch + +* Tue Oct 27 2009 SME Translation Server 1.2-35.sme +- apply locale 2009-10-27 patch + +* Mon Aug 24 2009 SME Translation Server 1.2-34.sme +- apply locale 2009-08-24 patch + +* Sat Jun 13 2009 Stephen Noble 1.2-33 +- chroot path not displayed in panel [SME: 5360] + +* Mon Apr 27 2009 SME Translation Server 1.2-32 +- apply locale 2009-04-27 patch + +* Sun Mar 1 2009 Jonathan Martens 1.2-30 +- Apply 1 Mar 2009 locale patch [SME: 5018] + +* Thu Jan 1 2009 Jonathan Martens 1.2-29 +- Apply 1 Jan 2009 locale patch [SME: 4900] + +* Sun Nov 30 2008 Jonathan Martens 1.2-28 +- Apply 30 Nov 2008 locale patch + +* Tue Oct 14 2008 Jonathan Martens 1.2-27 +- Apply 14 Oct 2008 locale patch + +* Sat Sep 27 2008 Stephen Noble - 1.2-26 +- Apply locale patch + +* Tue Jul 1 2008 Jonathan Martens 1.2-25 +- Apply 1 July 2008 locale patch + +* Wed May 21 2008 Jonathan Martens 1.2-24 + Thu May 21 2008 --> Thu May 15 2008 or Wed May 21 2008 or Thu May 22 2008 or .... +- Apply 21 May 2008 locale patch + +* Mon May 5 2008 Jonathan Martens 1.2-23 +- Apply 5 May 2008 locale patch + +* Sat Apr 26 2008 Jonathan Martens 1.2-22 +- Add common tags to e-smith-formmagick's general + +* Tue Apr 22 2008 Jonathan Martens 1.2-21 +- Forgot to apply patch + +* Tue Apr 22 2008 Jonathan Martens 1.2-20 +- Apply 22 April 2008 locale patch + +* Tue Apr 1 2008 Shad L. Lords 1.2-19 +- Update to UTF-8 translations + +* Tue Mar 11 2008 Stephen Noble - 1.2-18 +- update locale 2008-03-11 + +* Sat Mar 07 2008 Stephen Noble - 1.2-17 +- prepare en lexicons for pootle translations + +* Fri Jan 11 2008 Stephen Noble 1.2-16 +- remove duplicate event rssh.conf [SME 3470] + +* Thu Dec 20 2007 Stephen Noble +- french menu fix 1.2-14 + +* Thu Dec 20 2007 Stephen Noble +- french translation, thanks Sylvain 1.2-13 + +* Wed Jun 13 2007 Stephen Noble +- apply changes from 1.2-2 to 1.2-12 + +* Sun Apr 29 2007 Shad L. Lords +- Clean up spec so package can be built by koji/plague + +* Sun Feb 18 2007 Stephen Noble +- swedish translation, thanks Chrille +- [1.2-12] + +* Tue Jan 23 2007 Stephen Noble +- spanish translation, thanks Gene +- requires e-smith-proftpd >= 1.12.0-6, custom template removed +- default set, ftp{ChrootDir} = home +- [1.2-11] + +* Thu Dec 07 2006 Shad L. Lords +- Update to new release naming. No functional changes. +- Make Packager generic + +* Thu Nov 23 2006 Stephen Noble +- chroot path fix when home set [sme 2084] +- [1.2-10] + +* Fri Nov 10 2006 Stephen Noble +- fix textarea bug [sme 1088] +- requires perl-CGI-FormMagick-0.92-08 +- [1.2-9] + +* Fri Nov 10 2006 Stephen Noble +- chroot path fix [sme 2046] +- [1.2-8] + +* Fri Nov 3 2006 Stephen Noble +- german translation fix +- [1.2-7] + +* Fri Aug 25 2006 Stephen Noble +- empty chroot path defaults to home [sme 1249] +- [1.2-6] + +* Thu Aug 24 2006 Stephen Noble +- now finds correct sshkeys when used under userpanel +- [1.2-5] + +* Wed May 10 2006 Stephen Noble +- German translation fixed [sme 1258] +- [1.2-4] + +* Wed May 10 2006 Stephen Noble +- RSSH access uses VPNAccess property +- German translation added, thanks Dietmar +- [1.2-3] + +* Mon Apr 24 2006 Stephen Noble +- Description Display fixed +- [1.2-2] + +* Fri Apr 14 2006 Stephen Noble +- FormMagick Version +- [1.2-1] + +* Thu Apr 13 2006 Stephen Noble +- merged sshkeys panel and functions +- [1.0-13] + +* Wed Apr 12 2006 Stephen Noble +- possible fix for Insecure dependency on rc1 +- [1.0-12] + +* Wed Apr 12 2006 Stephen Noble +- option to set VPN Client Access +- uses user-modify event +- [1.0-11] + +* Thu Feb 23 2006 Stephen Noble +- proftp.conf/05chroot added as custom template for now +- defaults all users to ~/home +- Shell db settings changed was LoginShell +- [1.0-10] + +* Thu Feb 23 2006 Stephen Noble +- global/individual rssh clarified +- global reset removed +- chroot db settings changed +- [1.0-9] + +* Tue Feb 21 2006 Stephen Noble +- SME 7 pre3 version +- [1.0-8] + +* Thu Aug 11 2005 Stephen Noble +- SME 7 release +- [1.0-7] + +* Sun Jul 17 2005 Stephen Noble +- Merge of e-smith-usershellaccess & dungog-chroot-proftp +- original elements by Daniel van Raay & Damien Curtain +- [1.0-1] + +%prep +%setup + +mkdir -p root/etc/e-smith/events/smeserver-remoteuseraccess-update + +%build +perl createlinks + +LEXICONS=$(find root/etc/e-smith/{locale/,web/functions/} -type f ) + +for lexicon in $LEXICONS +do + /sbin/e-smith/validate-lexicon $lexicon +done + +LINKS=$(find root/etc/e-smith/locale/ -type d -maxdepth 1 | sed 's/root\/etc\/e-smith\/locale\///') +for link in $LINKS +do + /bin/ln -s remoteuseraccess root/etc/e-smith/locale/$link/etc/e-smith/web/functions/userpanel-sshkeys +done + +%install +rm -rf $RPM_BUILD_ROOT +(cd root ; find . -depth -print | cpio -dump $RPM_BUILD_ROOT) +rm -f %{name}-%{version}-filelist +/sbin/e-smith/genfilelist $RPM_BUILD_ROOT > %{name}-%{version}-filelist +echo "%doc COPYING" >> %{name}-%{version}-filelist + +%clean +cd .. +rm -rf %{name}-%{version} + +%pre +%preun +%post + +%postun +#uninstalls not upgrades +if [ $1 = 0 ] ; then + echo "uninstall" +fi + +%files -f %{name}-%{version}-filelist +%defattr(-,root,root)