Hello community,
here is the log from the commit of package yast2-trans-fi
checked in at Fri Nov 17 19:02:05 CET 2006.
--------
--- yast2-trans-fi/yast2-trans-fi.changes 2006-11-16 15:08:19.000000000 +0100
+++ /mounts/work_src_done/NOARCH/yast2-trans-fi/yast2-trans-fi.changes 2006-11-17 16:30:20.000000000 +0100
@@ -1,0 +2,5 @@
+Fri Nov 17 16:30:20 2006 - ke@suse.de
+
+- Update to version 2.14.16.
+
+------------------------------------------------------------------------
Old:
----
yast2-trans-fi-2.14.15.tar.bz2
New:
----
yast2-trans-fi-2.14.16.tar.bz2
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ yast2-trans-fi.spec ++++++
--- /var/tmp/diff_new_pack.cVtC2h/_old 2006-11-17 19:02:02.000000000 +0100
+++ /var/tmp/diff_new_pack.cVtC2h/_new 2006-11-17 19:02:02.000000000 +0100
@@ -1,5 +1,5 @@
#
-# spec file for package yast2-trans-fi (Version 2.14.15)
+# spec file for package yast2-trans-fi (Version 2.14.16)
#
# Copyright (c) 2006 SUSE LINUX Products GmbH, Nuernberg, Germany.
# This file and all modifications and additions to the pristine
@@ -11,12 +11,12 @@
# norootforbuild
Name: yast2-trans-fi
-Version: 2.14.15
+Version: 2.14.16
Release: 1
License: GNU General Public License (GPL)
Group: System/YaST
BuildRoot: %{_tmppath}/%{name}-%{version}-build
-Source0: yast2-trans-fi-2.14.15.tar.bz2
+Source0: yast2-trans-fi-2.14.16.tar.bz2
prefix: /usr
Provides: locale(yast2:fi)
BuildRequires: pkgconfig yast2-devtools
@@ -30,7 +30,7 @@
%prep
-%setup -n yast2-trans-fi-2.14.15
+%setup -n yast2-trans-fi-2.14.16
%build
autoreconf --force --install
@@ -62,6 +62,8 @@
/usr/share/YaST2/locale
%changelog -n yast2-trans-fi
+* Fri Nov 17 2006 - ke@suse.de
+- Update to version 2.14.16.
* Thu Nov 16 2006 - ke@suse.de
- Update to version 2.14.15.
* Tue Nov 14 2006 - ke@suse.de
++++++ yast2-trans-fi-2.14.15.tar.bz2 -> yast2-trans-fi-2.14.16.tar.bz2 ++++++
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-trans-fi-2.14.15/VERSION new/yast2-trans-fi-2.14.16/VERSION
--- old/yast2-trans-fi-2.14.15/VERSION 2006-11-16 15:08:19.000000000 +0100
+++ new/yast2-trans-fi-2.14.16/VERSION 2006-11-17 16:30:20.000000000 +0100
@@ -1 +1 @@
-2.14.15
+2.14.16
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-trans-fi-2.14.15/configure new/yast2-trans-fi-2.14.16/configure
--- old/yast2-trans-fi-2.14.15/configure 2006-11-16 15:08:28.000000000 +0100
+++ new/yast2-trans-fi-2.14.16/configure 2006-11-17 16:30:30.000000000 +0100
@@ -1,6 +1,6 @@
#! /bin/sh
# Guess values for system-dependent variables and create Makefiles.
-# Generated by GNU Autoconf 2.60 for yast2-trans-fi 2.14.15.
+# Generated by GNU Autoconf 2.60 for yast2-trans-fi 2.14.16.
#
# Report bugs to http://bugs.opensuse.org/.
#
@@ -559,8 +559,8 @@
# Identity of this package.
PACKAGE_NAME='yast2-trans-fi'
PACKAGE_TARNAME='yast2-trans-fi'
-PACKAGE_VERSION='2.14.15'
-PACKAGE_STRING='yast2-trans-fi 2.14.15'
+PACKAGE_VERSION='2.14.16'
+PACKAGE_STRING='yast2-trans-fi 2.14.16'
PACKAGE_BUGREPORT='http://bugs.opensuse.org/'
ac_unique_file="RPMNAME"
@@ -1185,7 +1185,7 @@
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
-\`configure' configures yast2-trans-fi 2.14.15 to adapt to many kinds of systems.
+\`configure' configures yast2-trans-fi 2.14.16 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@@ -1256,7 +1256,7 @@
if test -n "$ac_init_help"; then
case $ac_init_help in
- short | recursive ) echo "Configuration of yast2-trans-fi 2.14.15:";;
+ short | recursive ) echo "Configuration of yast2-trans-fi 2.14.16:";;
esac
cat <<\_ACEOF
@@ -1336,7 +1336,7 @@
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
-yast2-trans-fi configure 2.14.15
+yast2-trans-fi configure 2.14.16
generated by GNU Autoconf 2.60
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
@@ -1350,7 +1350,7 @@
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
-It was created by yast2-trans-fi $as_me 2.14.15, which was
+It was created by yast2-trans-fi $as_me 2.14.16, which was
generated by GNU Autoconf 2.60. Invocation command line was
$ $0 $@
@@ -2151,7 +2151,7 @@
# Define the identity of the package.
PACKAGE='yast2-trans-fi'
- VERSION='2.14.15'
+ VERSION='2.14.16'
cat >>confdefs.h <<_ACEOF
@@ -2378,7 +2378,7 @@
-VERSION="2.14.15"
+VERSION="2.14.16"
RPMNAME="yast2-trans-fi"
MAINTAINER="Karl Eichwalder "
@@ -3313,7 +3313,7 @@
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
-This file was extended by yast2-trans-fi $as_me 2.14.15, which was
+This file was extended by yast2-trans-fi $as_me 2.14.16, which was
generated by GNU Autoconf 2.60. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@@ -3356,7 +3356,7 @@
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF
ac_cs_version="\\
-yast2-trans-fi config.status 2.14.15
+yast2-trans-fi config.status 2.14.16
configured by $0, generated by GNU Autoconf 2.60,
with options \\"`echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-trans-fi-2.14.15/configure.in new/yast2-trans-fi-2.14.16/configure.in
--- old/yast2-trans-fi-2.14.15/configure.in 2006-11-16 15:08:25.000000000 +0100
+++ new/yast2-trans-fi-2.14.16/configure.in 2006-11-17 16:30:26.000000000 +0100
@@ -3,7 +3,7 @@
dnl -- This file is generated by y2autoconf 2.14.0 - DO NOT EDIT! --
dnl (edit configure.in.in instead)
-AC_INIT(yast2-trans-fi, 2.14.15, http://bugs.opensuse.org/, yast2-trans-fi)
+AC_INIT(yast2-trans-fi, 2.14.16, http://bugs.opensuse.org/, yast2-trans-fi)
dnl Check for presence of file 'RPMNAME'
AC_CONFIG_SRCDIR([RPMNAME])
@@ -17,7 +17,7 @@
AM_INIT_AUTOMAKE(tar-ustar) dnl searches for some needed programs
dnl Important YaST2 variables
-VERSION="2.14.15"
+VERSION="2.14.16"
RPMNAME="yast2-trans-fi"
MAINTAINER="Karl Eichwalder "
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-trans-fi-2.14.15/po/status.txt new/yast2-trans-fi-2.14.16/po/status.txt
--- old/yast2-trans-fi-2.14.15/po/status.txt 2006-11-16 14:19:21.000000000 +0100
+++ new/yast2-trans-fi-2.14.16/po/status.txt 2006-11-17 14:46:12.000000000 +0100
@@ -1,6 +1,6 @@
-Translated : 16377
+Translated : 16385
Fuzzy : 1
-Untranslated : 9
+Untranslated : 1
--------------------
All strings : 16387
100 % are translated
diff -urN --exclude=CVS --exclude=.cvsignore --exclude=.svn --exclude=.svnignore old/yast2-trans-fi-2.14.15/po/yast2-apparmor.fi.po new/yast2-trans-fi-2.14.16/po/yast2-apparmor.fi.po
--- old/yast2-trans-fi-2.14.15/po/yast2-apparmor.fi.po 2006-11-10 15:00:50.000000000 +0100
+++ new/yast2-trans-fi-2.14.16/po/yast2-apparmor.fi.po 2006-11-17 14:46:10.000000000 +0100
@@ -13,7 +13,7 @@
"Project-Id-Version: yast2-apparmor.fi\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2006-11-03 13:45-0800\n"
-"PO-Revision-Date: 2006-11-10 05:46+0200\n"
+"PO-Revision-Date: 2006-11-17 14:36+0200\n"
"Last-Translator: Jyri Palokangas \n"
"Language-Team: Suomi \n"
"MIME-Version: 1.0\n"
@@ -36,15 +36,15 @@
#: apparmor_profile_check.ycp:42
msgid "<p>Comprehensive documentation about AppArmor is available in the users guide for the distribution. This is available in the directory: "
-msgstr ""
+msgstr "<p>Jakeluversion käyttöoppaassa on laaja dokumentaatio AppArmoria koskien. Tämä löytyy hakemistosta: "
#: apparmor_profile_check.ycp:47
msgid "<p>Please refer to this for more detailed information about AppArmor</p>"
-msgstr ""
+msgstr "<p>Käytä sitä etsiessäsi lisätietoja AppArmorista.</p>"
#: config_complain.ycp:14
msgid "<p><b>Profile Mode Configuration</b><br>This tool allows you to set AppArmor profiles to either complain or enforce mode.</p><p>Complain mode is a profile training state that logs application activity, but does not restrict the application's behavior.</p><p>Profiles in enforce mode are protected by AppArmor.</p>"
-msgstr ""
+msgstr "<p><b>Profiilin tilan määritys</b><br>Tämän työkalun avulla voit asettaa AppArmorin profiilit joko tarkkailu- tai pakotustilaan.</p><p>Tarkkailutilassa profiili ottaa ohjelman lokit talteen, mutta ei rajota ohjelman toimintaa.</p><p>Pakotustilassa olevat profiilit on suojattu AppArmorin avulla.</p>"
#: config_complain.ycp:28
msgid "Couldn't recognize profile name: "
@@ -198,17 +198,18 @@
#: GenProf.ycp:36 LogProf.ycp:36
msgid "&Scan system log for AppArmor events"
-msgstr ""
+msgstr "&Skannaa järjestelmälokista AppArmorin tapahtumat"
#: GenProf.ycp:51 GenProf.ycp:70 LogProf.ycp:52 LogProf.ycp:71
msgid "Synchronization error between frontend and backend."
-msgstr ""
+msgstr "Synkronisointivirhe graafisen käyttöliittymän ja taustaohjelman välillä."
#: GenProf.ycp:79 LogProf.ycp:80
msgid "AppArmor Profile Wizard"
msgstr "AppArmor profiiliwelho"
#: GenProf.ycp:80
+#, fuzzy
msgid ""
" <b>AppArmor Profiling Wizard</b><br>\n"
" This wizard presents entries generated by the AppArmor access control module. You can generate highly optimized and robust security profiles by using the suggestions made by AppArmor. AppArmor suggests that you allow or deny access to specific resources or define execute permission for entries. These questions that display were logged during the normal application execution test previously performed. <br>\n"
@@ -347,6 +348,142 @@
" <li>TMPDIR</li>\n"
" <li>TZDIR</li> </ul>\n"
msgstr ""
+" <b>AppArmor profilointi welho</b><br>\n"
+" Tämä welho esittää AppArmor pääsynvalvonta moduulin luomat merkinnät. Voit luoda pitkälle optimoituja ja vankkoja tietoturva profiileja käyttämällä AppArmorin ehdotuksia. AppArmor ehdottaa että joko sallit tai estät pääsyn määrittettyyn resurssiin tai määrität suoritusoikeudet merkinnöille. Nämä näytettävät kysymykset kirjattiin aiemmin suoritetun normaalin sovelluksen suoritustestin aikana. <br>\n"
+" Seuraava ohjeteksti kuvaa yksityiskohtaisesti AppArmorin tietoturvaprofiilissa käyttämää syntaksia. <br><br>Missä tahansa vaiheessa, voit muokata profiili merkintöjä vaihtamalla ehdotettua vastausta. Tämä yhteenveto avustaa sinua valinnoissasi. Katso lisätietoja ja vaihe vaiheelta ohje Admin käyttöohjeesta.\n"
+"<br><br>\n"
+" <b>Käyttötilat</b><br>\n"
+"\n"
+" Tiedosto oikeuksien käyttötilat koostuvat \n"
+" kuuden tilan yhdistelmistä:\n"
+"\n"
+"<ul> <li>r - luku</li>\n"
+" <li>w - kirjoitus</li>\n"
+" <li>m - mmap PROT_EXEC</li>\n"
+" <li>px - erillinen profiilin suoritus</li>\n"
+" <li>ux - rajoittamaton suoritus</li>\n"
+" <li>ix - peri suoritus</li>\n"
+" <li>l - linkki</li>\n"
+"</ul>\n"
+"<p>\n"
+" <br> <b>Käyttötilojen yksityiskohdat</b>\n"
+"<br><br>\n"
+" <b>Luku tilab><br>\n"
+" Sallii ohjelmalle lukuoikeuden\n"
+" resurssiin. Luku tila vaaditaan komentorivi srkipteiltä\n"
+" ja muilta tulkattavilta sisällöiltä, ja määrittää jos\n"
+" suoritettava prosessi voi executing process can core dump or be attached to with\n"
+" ptrace(2). (ptrace(2) is used by utilities such as\n"
+" strace(1), ltrace(1), and gdb(1).)\n"
+" <br>\n"
+" <br>\n"
+" <b>Write mode</b><br>\n"
+" Allows the program to have write access to the\n"
+" resource. Files must have this permission if they are\n"
+" to be unlinked (removed.)\n"
+" <br>\n"
+" <br>\n"
+" <b>Mmap PROT_EXEC mode</b><br>\n"
+" Allows the program to call mmap with PROT_EXEC on the\n"
+" resource. \n"
+" <br>\n"
+" <br>\n"
+" \n"
+"\n"
+" <b>Unconfined execute mode</b><br>\n"
+" \n"
+" Allows the program to execute the resource without any\n"
+" AppArmor profile being applied to the executed\n"
+" resource. Requires listing execute mode as well.\n"
+" Incompatible with Inherit and Discrete Profile execute\n"
+" entries.\n"
+" <br><br>\n"
+"\n"
+" This mode is useful when a confined program needs to\n"
+" be able to perform a privileged operation, such as\n"
+" rebooting the machine. By placing the privileged section \n"
+" in another executable and granting unconfined \n"
+" execution rights, it is possible to bypass the mandatory \n"
+" constraints imposed on all confined processes.\n"
+" For more information on what is constrained, see the\n"
+" subdomain(7) man page.\n"
+"<br><br> <b>Discrete Profile execute mode</b><br>\n"
+" This mode requires that a discrete security profile is\n"
+" defined for a resource executed at a AppArmor domain\n"
+" transition. If there is no profile defined then the\n"
+" access will be denied. Incompatible with Inherit and\n"
+" Unconstrained execute entries.\n"
+" <br>\n"
+" <br> \n"
+" <b>Link mode</b><br>\n"
+" Allows the program to be able to create and remove a\n"
+" link with this name (including symlinks). When a link\n"
+" is created, the file that is being linked to MUST have\n"
+" the same access permissions as the link being created\n"
+" (with the exception that the destination does not have\n"
+" to have link access.) Link access is required for\n"
+" unlinking a file.\n"
+" <br>\n"
+" <br>\n"
+" <b>Globbing</b>\n"
+" <br>\n"
+" <br>\n"
+" File resources may be specified with a globbing syntax\n"
+" similar to that used by popular shells, such as csh(1),\n"
+" bash(1), zsh(1).\n"
+" <br>\n"
+"\n"
+" <ul>\n"
+"\t<li><b>*</b> can substitute for any number of characters, excepting\n"
+" '/'<li>\n"
+"\n"
+" \t<li><b>**</b> can substitute for any number of characters, including '/'</li>\n"
+"\n"
+"\n"
+" <li><b>?</b> can substitute for any single character excepting '/'</li>\n"
+"\n"
+" <li><b>[abc]</b> will substitute for the single character a, b, or c</li>\n"
+"\n"
+" <li><b>[a-c]</b> will substitute for the single character a, b, or c</li>\n"
+"\n"
+" <li><b>{ab,cd}</b> will expand to one rule to match ab, one rule to match\n"
+" cd</li>\n"
+"\n"
+" </ul>\n"
+"\n"
+" <br>\n"
+" <br>\n"
+" <b>Clean Exec - for sanitized execution</b>\n"
+" <br>\n"
+" <br>\n"
+" The Clean Exec option for the discrete profile and unconstrained \n"
+" execute permissions provide added security by stripping the \n"
+" enviroment that is inherited by the child program of specific \n"
+" variables. You will be prompted to choose whether you want to sanitize the\n"
+" enviroment if you choose 'p' or 'u' during the profiling process.\n"
+" Muuttujia ovat:\n"
+" <ul> \n"
+" <li>GCONV_PATH</li>\n"
+" <li>GETCONF_DIR</li>\n"
+" <li>HOSTALIASES</li>\n"
+" <li>LD_AUDIT</li>\n"
+" <li>LD_DEBUG</li>\n"
+" <li>LD_DEBUG_OUTPUT</li>\n"
+" <li>LD_DYNAMIC_WEAK</li>\n"
+" <li>LD_LIBRARY_PATH</li>\n"
+" <li>LD_ORIGIN_PATH</li>\n"
+" <li>LD_PRELOAD</li>\n"
+" <li>LD_PROFILE</li>\n"
+" <li>LD_SHOW_AUXV</li>\n"
+" <li>LD_USE_LOAD_BIAS</li>\n"
+" <li>LOCALDOMAIN</li>\n"
+" <li>LOCPATH</li>\n"
+" <li>MALLOC_TRACE</li>\n"
+" <li>NLSPATH</li>\n"
+" <li>RESOLV_HOST_CONF</li>\n"
+" <li>RES_OPTION</li>\n"
+" <li>TMPDIR</li>\n"
+" <li>TZDIR</li> </ul>\n"
#: GenProf.ycp:333 LogProf.ycp:325
msgid "&Yes"
@@ -630,7 +767,7 @@
#: profile_dialogs.ycp:452
msgid "<b>*Clean Exec</b><br>The Clean Exec option for the discrete profile and unconstrained execute permissions provide added security by stripping the enviroment that is inherited by the child program of specific variables. These variables are:"
-msgstr ""
+msgstr "<b>*Clean Exec</b><br>\"Clean Exec\" valinta erilliselle profiilille ja rajoittamattomille suoritus oikeuksille, tarjoaa lisäturvaa poistamalla ympäristön jonka tiettyjen muuttujien lapsiohjelma perii. Nämä muuttujat ovat:"
#: profile_dialogs.ycp:529
msgid "Include entries can not be edited. Please select add or delete to manage Include entries."
@@ -653,9 +790,8 @@
msgstr "Valitse profiili, jota haluat muokata"
#: report_helptext.ycp:15
-#, fuzzy
msgid "The Report Configuration dialog enables you to filter the archived report selected in the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click <b>Filter By Date Range</b>. The fields become active. <li>Enter the start and end dates that delineate the scope of the report. <li>Enter other filtering parameters. See below for definitions of parameters. </ol> The following definitions help you to enter the filtering parameters in the Report Configuration Dialog: <br><br> <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the binary executable of the program of interest, the report will display security events that have occurred for a specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the name of the profile, the report will display the security events that are generated for the specified profile. You can use this to see what is being confined by a specific profile.<br><br> <b>PID Number:<
/b> Process ID number is a number that uniquely identifies one specific process or running program (this number is valid only during the lifetime of that process).<br><br> <b>Severity Level:</b> Select the lowest severity level for security events that you would like to be included in the report. The selected severity level, and above, will be included in the reports.<br><br> <b>Detail:</b> A source to which the profile has denied access. This includes capabilities and files. You can use this field to report the resources are not allowed to be accessed by profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile grants to the program or process to which it is applied. The options are: r (read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access type describes what is actually happening with the security event. The options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> Enables you to export a CSV (comma separated val
ues) or html file. The CSV file separates pieces of data in the log entries with commas using a standard data format for importing into table-oriented applications. You can enter a pathname for your exported report by typing in the full pathname in the field provided."
-msgstr "Raportin määritysikkuna mahdollistaa edellisessä ikkunassa valitun arkistoidun raportin rajaamisen. rajataksesi <b>Päivämäärävälillä:</b><br><br> <ol> <li>Napsauta <b>Rajaa päivämäärävälillä</b>. => Kentät otetaan käyttöön. <li>Anna alku- ja loppupäivämäärä, jotka rajaavat raportin haluamallesi välille. <li>Syötä muut rajausarvot. Katso ao. arvojen kuvaukset. </ol> Seuraavat kuvaukset auttavat rajausarvojen antamisessa raportin määritysikkunassa: <br><br> <b>Ohjelman nimi -maski:</b> Kun annat ohjelman nimen tai nimimaskin, joka täsmää suoritettavan tiedoston nimeen, raportti näyttää tapahtumat, jotka kohdistuvat tähän sovellukseen.<br><br> <b>Profiilin nimimaski:</b> Kun annat profiilin nimen, raportti näyttää tapahtumat, jotka kohdistuvat tähän profiiliin.<br><br> <b>PID-numero:</b> Prosessitunniste on numero, joka yksilöi yhden suoritettavan prosessin tai ohjelman (PID on voimassa vain prosessin elinaikana).<br><br>
<b>Vakavuustaso:</b> Valitse alin vakavuustaso, jonka haluat mukaan raporteille. Valitun tason ja sen yläpuolisten tasojen tapahtumat otetaan mukaan.<br><br> <b>Tiedot:</b> Lähde, johon profiili on estänyt pääsyn. Tämä sisältää kyvyt ja tiedostot. Tätä kenttää voidaan käyttää listaamaan resurssit, joiden käyttö ei ole sallittua eri profiileilla.<br><br> <b>Tila:</b> Tila on käyttöoikeus, jonka profiili antaa ohjelmalle tai prosessille. Valinnat ovat : r (luku) w (kirjoitus) l (linkitys) x (suoritus)<br><br> <b>Käsittely:</b> kuvaa, miten tapahtuma käsiteltiin. Vaihtoehdot ovat: SALLITTIIN, HYLÄTTIIN tai TARKASTETTIIN.<br><br> <b>CSV tai HTML:</b> CSV- (pilkulla erotellut arvot) tai HTML -muotoisen tiedoston vientitoiminto. CSV-muoto erottelee kirjausmerkintöjen sarakkeet taulukkotyyppisten sovellusten hyväksymällä tavalla. Vietävän raportin polun nimi annetaan kirjoittamalla täysi polkunimi kenttään."
+msgstr "Raportin määritysikkuna mahdollistaa edellisessä ikkunassa valitun arkistoidun raportin rajaamisen. Rajataksesi <b>Päivämäärävälillä:</b><br><br> <ol> <li>Napsauta <b>Rajaa päivämäärävälillä</b>. => Kentät otetaan käyttöön. <li>Anna alku- ja loppupäivämäärä, jotka rajaavat raportin haluamallesi välille. <li>Syötä muut rajausarvot. Katso ao. arvojen kuvaukset. </ol> Seuraavat kuvaukset auttavat rajausarvojen antamisessa raportin määritysikkunassa: <br><br> <b>Ohjelman nimi -maski:</b> Kun annat ohjelman nimen tai nimimaskin, joka täsmää suoritettavan tiedoston nimeen, raportti näyttää tapahtumat, jotka kohdistuvat tähän sovellukseen.<br><br> <b>Profiilin nimimaski:</b> Kun annat profiilin nimen, raportti näyttää tapahtumat, jotka kohdistuvat tähän profiiliin.<br><br> <b>PID-numero:</b> Prosessitunniste on numero, joka yksilöi yhden suoritettavan prosessin tai ohjelman (PID on voimassa vain prosessin elinaikana).<br><br>
<b>Vakavuustaso:</b> Valitse alin vakavuustaso, jonka haluat mukaan raporteille. Valitun tason ja sen yläpuolisten tasojen tapahtumat otetaan mukaan.<br><br> <b>Tiedot:</b> Lähde, johon profiili on estänyt pääsyn. Tämä sisältää kyvyt ja tiedostot. Tätä kenttää voidaan käyttää listaamaan resurssit, joiden käyttö ei ole sallittua eri profiileilla.<br><br> <b>Tila:</b> Tila on käyttöoikeus, jonka profiili antaa ohjelmalle tai prosessille. Valinnat ovat : r (luku) w (kirjoitus) l (linkitys) x (suoritus)<br><br> <b>Käsittely:</b> kuvaa, miten tapahtuma käsiteltiin. Vaihtoehdot ovat: SALLITTIIN, HYLÄTTIIN tai TARKASTETTIIN.<br><br> <b>CSV tai HTML:</b> CSV- (pilkulla erotellut arvot) tai HTML -muotoisen tiedoston vientitoiminto. CSV-muoto erottelee kirjausmerkintöjen sarakkeet taulukkotyyppisten sovellusten hyväksymällä tavalla. Vietävän raportin polun nimi annetaan kirjoittamalla täysi polkunimi kenttään."
#: report_helptext.ycp:18
msgid "The AppArmor On-Demand Report screen displays an instantly generated version of one of the following reports. <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally confined applications during a specific time period. You can edit and customize this report, or add new versions."
@@ -667,7 +803,7 @@
#: report_helptext.ycp:26
msgid "<b>Generate Reports Help</b> <p>If there were, in fact, going to be any help for you (which, incidentally, there isn't going to be), then you would indeed find said help, here.<p> Thank you for your time, and have a nice day."
-msgstr ""
+msgstr "<b>Luo raportin ohje</b> <p>Jos tässä olisi, tai oikeastaan, tulisi olemaan ohje (jota ei, kuitenkaan tule), voisit löytää tuon mainitun ohjeen tästä.<p> Kiitos ajastasi, ja hauskaa päivän jatkoa."
#: report_helptext.ycp:31
msgid "The summary of scheduled reports page shows us when reports are scheduled to run. Reports can be set to run monthly, weekly, daily, or hourly. The default settings are daily at midnight. The reports can also be emailed, upon completion, to up to three email recipients.<br><br> In the Set Schedule section, you can schedule the following three types of security reports:<br><br> <b>Executive Security Summary:</b> A combined report, consisting of one or more Security incident reports from one or more machines. This report provides a single view of security events on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that reports which application servers are running and whether the applications are confined by AppArmor. Application servers are applications that accept incoming network connections. <br><br> <b>Security Incident Report:</b> A report that displays application security for a single host. It reports policy violations for locally co
nfined applications during a specific time period. You can edit and customize this report, or add new versions."
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Remember to have fun...
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-commit+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-commit+help@opensuse.org