Author: kmachalkova Date: Wed Apr 2 14:55:51 2008 New Revision: 45961 URL: http://svn.opensuse.org/viewcvs/yast?rev=45961&view=rev Log: fixed typos (#374628) Modified: trunk/apparmor/src/agents/ag_genprof trunk/apparmor/src/clients/GenProf.ycp trunk/apparmor/src/clients/LogProf.ycp trunk/apparmor/src/include/subdomain/apparmor_ycp_utils.ycp trunk/apparmor/src/include/subdomain/capabilities.ycp trunk/apparmor/src/include/subdomain/profile_dialogs.ycp trunk/apparmor/src/include/subdomain/report_helptext.ycp Modified: trunk/apparmor/src/agents/ag_genprof URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/agents/ag_genprof?re... ============================================================================== --- trunk/apparmor/src/agents/ag_genprof (original) +++ trunk/apparmor/src/agents/ag_genprof Wed Apr 2 14:55:51 2008 @@ -68,7 +68,7 @@ application behavior. Please enter the application name for which you would like -to create a profile, or selecte Browse to find the +to create a profile, or select Browse to find the application on your system."), file_label => gettext("&Application to Profile"), okay_label => gettext("&Create"), Modified: trunk/apparmor/src/clients/GenProf.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/clients/GenProf.ycp?... ============================================================================== --- trunk/apparmor/src/clients/GenProf.ycp (original) +++ trunk/apparmor/src/clients/GenProf.ycp Wed Apr 2 14:55:51 2008 @@ -172,7 +172,7 @@ <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 + environment that is inherited by the child program of specific variables. You will be prompted to choose whether you want to sanitize the enviroment if you choose 'p' or 'u' during the profiling process. The variables are: Modified: trunk/apparmor/src/clients/LogProf.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/clients/LogProf.ycp?... ============================================================================== --- trunk/apparmor/src/clients/LogProf.ycp (original) +++ trunk/apparmor/src/clients/LogProf.ycp Wed Apr 2 14:55:51 2008 @@ -172,7 +172,7 @@ execute permissions provide added security by stripping the enviroment that is inherited by the child program of specific variables. You will be prompted to choose whether you want to sanitize the - enviroment if you choose 'p' or 'u' during the profiling process. + environment if you choose 'p' or 'u' during the profiling process. The variables are: <ul> <li>GCONV_PATH</li> Modified: trunk/apparmor/src/include/subdomain/apparmor_ycp_utils.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/include/subdomain/ap... ============================================================================== --- trunk/apparmor/src/include/subdomain/apparmor_ycp_utils.ycp (original) +++ trunk/apparmor/src/include/subdomain/apparmor_ycp_utils.ycp Wed Apr 2 14:55:51 2008 @@ -112,7 +112,7 @@ _("S&ave configuration")), `HSpacing( 0.5), `Left(`PushButton(`id(`signin_submit), - _("&Signin"))), + _("&Sign in"))), `Right(`PushButton(`id(`signin_cancel), _("&Cancel"))), `HSpacing( 0.5) Modified: trunk/apparmor/src/include/subdomain/capabilities.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/include/subdomain/ca... ============================================================================== --- trunk/apparmor/src/include/subdomain/capabilities.ycp (original) +++ trunk/apparmor/src/include/subdomain/capabilities.ycp Wed Apr 2 14:55:51 2008 @@ -144,7 +144,7 @@ "sys_admin" : $[ "name" : "CAP_SYS_ADMIN", - "info" : _("<ul><li> Allow configuration of the secure attention key</li> <li> Allow administration of the random device</li> <li> Allow examination and configuration of disk quotas</li> <li> Allow configuring the kernel's syslog (printk behaviour)</li> <li> Allow setting the domainname</li> <li> Allow setting the hostname</li> <li> Allow calling bdflush()</li> <li> Allow mount() and umount(), setting up new smb connection</li> <li> Allow some autofs root ioctls</li> <li> Allow nfsservctl</li> <li> Allow VM86_REQUEST_IRQ</li> <li> Allow to read/write pci config on alpha</li> <li> Allow irix_prctl on mips (setstacksize)</li> <li> Allow flushing all cache on m68k (sys_cacheflush)</li> <li> Allow removing semaphores</li> <li> Used instead of CAP_CHOWN to "chown" IPC message queues, semaphores and shared memory</li> <li> Allow locking/unlocking of shared memory segment</li> <li> Allow turning swap on/off</li> <li> Allow forged pids on socket credentials passing</li> <li> Allow setting readahead and flushing buffers on block devices</li> <li> Allow setting geometry in floppy driver</li> <li> Allow turning DMA on/off in xd driver</li> <li> Allow administration of md devices (mostly the above, but some extra ioctls)</li> <li> Allow tuning the ide driver</li> <li> Allow access to the nvram device</li> <li> Allow administration of apm_bios, serial and bttv (TV) device</li> <li> Allow manufacturer commands in isdn CAPI support driver</li> <li> Allow reading non-standardized portions of pci configuration space</li> <li> Allow DDI debug ioctl on sbpcd driver</li> <li> Allow setting up serial ports</li> <li> Allow sending raw qic-117 commands</li> <li> Allow enabling/disabling tagged queuing on SCSI controllers and sending arbitrary SCSI commands</li> <li> Allow setting encryption key on loopback filesystem </li></ul>"), + "info" : _("<ul><li> Allow configuration of the secure attention key</li> <li> Allow administration of the random device</li> <li> Allow examination and configuration of disk quotas</li> <li> Allow configuring the kernel's syslog (printk behaviour)</li> <li> Allow setting the domain name</li> <li> Allow setting the hostname</li> <li> Allow calling bdflush()</li> <li> Allow mount() and umount(), setting up new smb connection</li> <li> Allow some autofs root ioctls</li> <li> Allow nfsservctl</li> <li> Allow VM86_REQUEST_IRQ</li> <li> Allow to read/write pci config on alpha</li> <li> Allow irix_prctl on mips (setstacksize)</li> <li> Allow flushing all cache on m68k (sys_cacheflush)</li> <li> Allow removing semaphores</li> <li> Used instead of CAP_CHOWN to "chown" IPC message queues, semaphores and shared memory</li> <li> Allow locking/unlocking of shared memory segment</li> <li> Allow turning swap on/off</li> <li> Allow forged pids on socket credentials passing</li> <li> Allow setting read ahead and flushing buffers on block devices</li> <li> Allow setting geometry in floppy driver</li> <li> Allow turning DMA on/off in xd driver</li> <li> Allow administration of md devices (mostly the above, but some extra ioctls)</li> <li> Allow tuning the ide driver</li> <li> Allow access to the nvram device</li> <li> Allow administration of apm_bios, serial and bttv (TV) device</li> <li> Allow manufacturer commands in isdn CAPI support driver</li> <li> Allow reading non-standardized portions of pci configuration space</li> <li> Allow DDI debug ioctl on sbpcd driver</li> <li> Allow setting up serial ports</li> <li> Allow sending raw qic-117 commands</li> <li> Allow enabling/disabling tagged queuing on SCSI controllers and sending arbitrary SCSI commands</li> <li> Allow setting encryption key on loopback filesystem </li></ul>"), ], "sys_boot" : Modified: trunk/apparmor/src/include/subdomain/profile_dialogs.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/include/subdomain/pr... ============================================================================== --- trunk/apparmor/src/include/subdomain/profile_dialogs.ycp (original) +++ trunk/apparmor/src/include/subdomain/profile_dialogs.ycp Wed Apr 2 14:55:51 2008 @@ -741,11 +741,11 @@ string help5 = _("<li><b>Directory</b><br>Add a directory entry to this profile</li>"); string help6 = _("<li><b>Capability</b><br>Add a capability entry to this profile</li>"); string help7 = _("<li><b>Include</b><br>Add an include entry to this profile. This option includes the profile entry contents of another file in this profile at load time.</li>"); - string help_net = _("<li><b>Network Entry</b><br>Add a network rule entry to this profile. This option will allow you to specificy network access privileges for the profile. You may specify a network address family and socket type.</li>"); + string help_net = _("<li><b>Network Entry</b><br>Add a network rule entry to this profile. This option will allow you to specify network access privileges for the profile. You may specify a network address family and socket type.</li>"); string helpHat = _("<li><b>Hat</b><br>Add a sub-profile for this profile - called a Hat. This option is analagous to manually creating a new profile, which can selected during execution only in the context of being asked for by a <b>changehat aware</b> application. For more information on changehat please see <b>man changehat</b> on your system or the Novell AppArmor User's Guide.</li>"); string helpEdit = _("</ul><p><b>Edit Entry:</b><br>Edit the selected entry.<p>"); string help8 = _("<b>Delete Entry:</b><br>Removes the selected entry from this profile.<p>"); - string help9 = _("<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:"); + string help9 = _("<b>*Clean Exec</b><br>The Clean Exec option for the discrete profile and unconstrained execute permissions provide added security by stripping the environment that is inherited by the child program of specific variables. These variables are:"); string help10 = "<ul> <li>GCONV_PATH</li><li>GETCONF_DIR</li><li>HOSTALIASES</li><li>LD_AUDIT</li><li>LD_DEBUG</li><li>LD_DEBUG_OUTPUT</li><li>LD_DYNAMIC_WEAK</li><li>LD_LIBRARY_PATH</li><li>LD_ORIGIN_PATH</li><li>LD_PRELOAD</li><li>LD_PROFILE</li><li>LD_SHOW_AUXV</li><li>LD_USE_LOAD_BIAS</li><li>LOCALDOMAIN</li><li>LOCPATH</li><li>MALLOC_TRACE</li><li>NLSPATH</li><li>RESOLV_HOST_CONF</li><li>RES_OPTION</li><li>TMPDIR</li><li>TZDIR</li></ul><p> "; @@ -959,7 +959,7 @@ foreach( string pathItem, (list<string>) validIncludes, { pathListMsg = pathListMsg + "\n " + pathItem; }); - Popup::Error(_("Invalid #include file. Include files must be located in one of these directores: \n") + pathListMsg ); + Popup::Error(_("Invalid #include file. Include files must be located in one of these directories: \n") + pathListMsg ); } else { string includeName = substring(newInclude, 16 ); includes = add( includes, includeName, 1 ); Modified: trunk/apparmor/src/include/subdomain/report_helptext.ycp URL: http://svn.opensuse.org/viewcvs/yast/trunk/apparmor/src/include/subdomain/re... ============================================================================== --- trunk/apparmor/src/include/subdomain/report_helptext.ycp (original) +++ trunk/apparmor/src/include/subdomain/report_helptext.ycp Wed Apr 2 14:55:51 2008 @@ -17,7 +17,7 @@ string runHelp = _("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."); -string filterCfHelp1 = _("The Report Configuration dialog enables you to filter the 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: <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the executable process 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 security profile that is applied to the rocess, 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 values) 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.<br><br>"); +string filterCfHelp1 = _("The Report Configuration dialog enables you to filter the 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: <b>Program Name Pattern:</b> When you enter a program name or pattern that matches the name of the executable process 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 security profile that is applied to the process, 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 values) 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.<br><br>"); /* START Help Section -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org