1
# yast2-apparmor locale file
2
# Copyright (C) 2005 Novell INC.
3
# This file is distributed under the same license as the yast2-apparmor package.
4
# David Drewelow <davidd@immunix.com>, 2005.
9
"Project-Id-Version: yast2 AppArmor 1.2\n"
10
"Report-Msgid-Bugs-To: apparmor-general@forge.novell.com\n"
11
"POT-Creation-Date: 2005-04-01 14:07-0800\n"
12
"PO-Revision-Date: 2005-04-15 09:10+8\n"
13
"Last-Translator: Jesse Michael <jesse@immunix.com>\n"
14
"Language-Team: English\n"
16
"Content-Type: text/plain; charset=UTF-8\n"
17
"Content-Transfer-Encoding: 8bit\n"
19
#: profile_dialogs.ycp:218 reporting_dialogues.ycp:1079
20
#: reporting_dialogues.ycp:1756 reporting_dialogues.ycp:2054
21
msgid "Select Directory"
22
msgstr "Select Directory"
24
#: profile_dialogs.ycp:220
28
#: profile_dialogs.ycp:261
29
msgid "Entry will not added. Entry name or permissions not defined."
30
msgstr "Entry will not added. Entry name or permissions not defined."
32
#: profile_dialogs.ycp:336
33
msgid "&Hat name to add"
34
msgstr "&Hat name to add"
36
#: profile_dialogs.ycp:450 reporting_dialogues.ycp:678
37
#: reporting_dialogues.ycp:1038 reporting_dialogues.ycp:1066
38
#: reporting_dialogues.ycp:1074 reporting_dialogues.ycp:1090
39
#: reporting_dialogues.ycp:1108 reporting_dialogues.ycp:1120
40
#: reporting_dialogues.ycp:1132 reporting_dialogues.ycp:1183
41
#: reporting_dialogues.ycp:1209 reporting_dialogues.ycp:1232
42
#: reporting_dialogues.ycp:1248 reporting_dialogues.ycp:1263
43
#: reporting_dialogues.ycp:1271 reporting_dialogues.ycp:1280
44
#: reporting_dialogues.ycp:1288 reporting_dialogues.ycp:1295
45
#: reporting_dialogues.ycp:1412 reporting_dialogues.ycp:1448
46
#: reporting_dialogues.ycp:1466 reporting_dialogues.ycp:1476
47
#: reporting_dialogues.ycp:1483 reporting_dialogues.ycp:1491
48
#: reporting_dialogues.ycp:1499 sd-config.ycp:79
52
#: profile_dialogs.ycp:478
54
"Include entries can not be edited. Please select add or delete to manage "
57
"Include entries can not be edited. Please select add or delete to manage "
60
#: profile_dialogs.ycp:596
61
msgid "Save changes to the Profile"
62
msgstr "Save changes to the Profile"
64
#: profile_dialogs.ycp:669
65
msgid "You must select a profile to edit"
66
msgstr "You must select a profile to edit"
68
#: report_helptext.ycp:5
70
"The Report Configuration dialog enables you to filter the archived report "
71
"selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
72
"<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
73
"<li>Enter the start and end dates that delineate the scope of the report. "
75
"The Report Configuration dialog enables you to filter the archived report "
76
"selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
77
"<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
78
"<li>Enter the start and end dates that delineate the scope of the report. "
80
#: profile_dialogs.ycp:574
81
msgid "Select File To Include"
82
msgstr "Select File To Include"
84
#: report_helptext.ycp:5
86
"The Report Configuration dialog enables you to filter the archived report "
87
"selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
88
"<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
89
"<li>Enter the start and end dates that delineate the scope of the report. "
90
"<li>Enter other filtering parameters. See below for definitions of "
91
"parameters. </ol> The following definitions help you to enter the filtering "
92
"parameters in the Report Configuration Dialog: <br><br> <b>Program Name "
93
"Pattern:</b> When you enter a program name or pattern that matches the name "
94
"of the binary executable of the program of interest, the report will display "
95
"security events that have occurred for a specific program.<br><br> "
96
"<b>Profile Name Pattern:</b> When you enter the name of the profile, the "
97
"report will display the security events that are generated for the specified "
98
"profile. You can use this to see what is being confined by a specific "
99
"profile.<br><br> <b>PID Number:</b> Process ID number is a number that "
100
"uniquely identifies one specific process or running program (this number is "
101
"valid only during the lifetime of that process).<br><br> <b>Severity Level:</"
102
"b> Select the lowest severity level for security events that you would like "
103
"to be included in the report. The selected severity level, and above, will "
104
"be included in the reports.<br><br> <b>Detail:</b> A source to which the "
105
"profile has denied access. This includes capabilities and files. You can "
106
"use this field to report the resources are not allowed to be accessed by "
107
"profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile "
108
"grants to the program or process to which it is applied. The options are: r "
109
"(read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access "
110
"type describes what is actually happening with the security event. The "
111
"options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
112
"Enables you to export a CSV (comma separated values) or html file. The CSV "
113
"file separates pieces of data in the log entries with commas using a "
114
"standard data format for importing into table-oriented applications. You can "
115
"enter a pathname for your exported report by typing in the full pathname in "
116
"the field provided."
118
"The Report Configuration dialog enables you to filter the archived report "
119
"selected in the previous screen. To filter by <b>Date Range:</b><br><br> "
120
"<ol> <li>Click <b>Filter By Date Range</b>. The fields become active. "
121
"<li>Enter the start and end dates that delineate the scope of the report. "
122
"<li>Enter other filtering parameters. See below for definitions of "
123
"parameters. </ol> The following definitions help you to enter the filtering "
124
"parameters in the Report Configuration Dialog: <br><br> <b>Program Name "
125
"Pattern:</b> When you enter a program name or pattern that matches the name "
126
"of the binary executable of the program of interest, the report will display "
127
"security events that have occurred for a specific program.<br><br> "
128
"<b>Profile Name Pattern:</b> When you enter the name of the profile, the "
129
"report will display the security events that are generated for the specified "
130
"profile. You can use this to see what is being confined by a specific "
131
"profile.<br><br> <b>PID Number:</b> Process ID number is a number that "
132
"uniquely identifies one specific process or running program (this number is "
133
"valid only during the lifetime of that process).<br><br> <b>Severity Level:</"
134
"b> Select the lowest severity level for security events that you would like "
135
"to be included in the report. The selected severity level, and above, will "
136
"be included in the reports.<br><br> <b>Detail:</b> A source to which the "
137
"profile has denied access. This includes capabilities and files. You can "
138
"use this field to report the resources are not allowed to be accessed by "
139
"profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile "
140
"grants to the program or process to which it is applied. The options are: r "
141
"(read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access "
142
"type describes what is actually happening with the security event. The "
143
"options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
144
"Enables you to export a CSV (comma separated values) or html file. The CSV "
145
"file separates pieces of data in the log entries with commas using a "
146
"standard data format for importing into table-oriented applications. You can "
147
"enter a pathname for your exported report by typing in the full pathname in "
148
"the field provided."
150
#: report_helptext.ycp:8
152
"The AppArmor On-Demand Report screen displays an instantly generated version "
153
"of one of the following reports. <b>Executive Security Summary:</b> A "
154
"combined report, consisting of one or more Security incident reports from "
155
"one or more machines. This report provides a single view of security events "
156
"on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing "
157
"tool that reports which application servers are running and whether the "
158
"applications are confined by AppArmor. Application servers are applications "
159
"that accept incoming network connections. <br><br> <b>Security Incident "
160
"Report:</b> A report that displays application security for a single host. "
161
"It reports policy violations for locally confined applications during a "
162
"specific time period. You can edit and customize this report, or add new "
165
"The AppArmor On-Demand Report screen displays an instantly generated version "
166
"of one of the following reports. <b>Executive Security Summary:</b> A "
167
"combined report, consisting of one or more Security incident reports from "
168
"one or more machines. This report provides a single view of security events "
169
"on multiple machines.<br><br> <b>Applications Audit Report:</b> An auditing "
170
"tool that reports which application servers are running and whether the "
171
"applications are confined by AppArmor. Application servers are applications "
172
"that accept incoming network connections. <br><br> <b>Security Incident "
173
"Report:</b> A report that displays application security for a single host. "
174
"It reports policy violations for locally confined applications during a "
175
"specific time period. You can edit and customize this report, or add new "
178
#: report_helptext.ycp:10
180
"The Report Configuration dialog enables you to filter the report selected in "
181
"the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click "
182
"<b>Filter By Date Range</b>. The fields become active. <li>Enter the start "
183
"and end dates that delineate the scope of the report. <li>Enter other "
184
"filtering parameters. See below for definitions of parameters. </ol> The "
185
"following definitions help you to enter the filtering parameters in the "
186
"Report Configuration Dialog: <b>Program Name Pattern:</b> When you enter a "
187
"program name or pattern that matches the name of the executable process of "
188
"interest, the report will display security events that have occurred for a "
189
"specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the "
190
"name of the security profile that is applied to the rocess, the report will "
191
"display the security events that are generated for the specified profile. "
192
"You can use this to see what is being confined by a specific profile."
193
"<br><br> <b>PID Number:</b> Process ID number is a number that uniquely "
194
"identifies one specific process or running program (this number is valid "
195
"only during the lifetime of that process).<br><br> <b>Severity Level:</b> "
196
"Select the lowest severity level for security events that you would like to "
197
"be included in the report. The selected severity level, and above, will be "
198
"included in the reports.<br><br> <b>Detail:</b> A source to which the "
199
"profile has denied access. This includes capabilities and files. You can "
200
"use this field to report the resources are not allowed to be accessed by "
201
"profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile "
202
"grants to the program or process to which it is applied. The options are: r "
203
"(read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access "
204
"type describes what is actually happening with the security event. The "
205
"options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
206
"Enables you to export a CSV (comma separated values) or html file. The CSV "
207
"file separates pieces of data in the log entries with commas using a "
208
"standard data format for importing into table-oriented applications. You can "
209
"enter a pathname for your exported report by typing in the full pathname in "
210
"the field provided.<br><br>"
212
"The Report Configuration dialog enables you to filter the report selected in "
213
"the previous screen. To filter by <b>Date Range:</b><br><br> <ol> <li>Click "
214
"<b>Filter By Date Range</b>. The fields become active. <li>Enter the start "
215
"and end dates that delineate the scope of the report. <li>Enter other "
216
"filtering parameters. See below for definitions of parameters. </ol> The "
217
"following definitions help you to enter the filtering parameters in the "
218
"Report Configuration Dialog: <b>Program Name Pattern:</b> When you enter a "
219
"program name or pattern that matches the name of the executable process of "
220
"interest, the report will display security events that have occurred for a "
221
"specific program.<br><br> <b>Profile Name Pattern:</b> When you enter the "
222
"name of the security profile that is applied to the rocess, the report will "
223
"display the security events that are generated for the specified profile. "
224
"You can use this to see what is being confined by a specific profile."
225
"<br><br> <b>PID Number:</b> Process ID number is a number that uniquely "
226
"identifies one specific process or running program (this number is valid "
227
"only during the lifetime of that process).<br><br> <b>Severity Level:</b> "
228
"Select the lowest severity level for security events that you would like to "
229
"be included in the report. The selected severity level, and above, will be "
230
"included in the reports.<br><br> <b>Detail:</b> A source to which the "
231
"profile has denied access. This includes capabilities and files. You can "
232
"use this field to report the resources are not allowed to be accessed by "
233
"profiles.<br><br> <b>Mode:</b> The Mode is the permission that the profile "
234
"grants to the program or process to which it is applied. The options are: r "
235
"(read) w (write) l (link) x (execute)<br><br> <b>Access Type:</b> The access "
236
"type describes what is actually happening with the security event. The "
237
"options are: PERMITTING, REJECTING, or AUDITING.<br><br> <b>CSV or HTML:</b> "
238
"Enables you to export a CSV (comma separated values) or html file. The CSV "
239
"file separates pieces of data in the log entries with commas using a "
240
"standard data format for importing into table-oriented applications. You can "
241
"enter a pathname for your exported report by typing in the full pathname in "
242
"the field provided.<br><br>"
244
#: report_helptext.ycp:13
246
"The summary of scheduled reports page shows us when reports are scheduled to "
247
"run. Reports can be set to run monthly, weekly, daily, or hourly. The "
248
"default settings are daily at midnight. The reports can also be emailed, "
249
"upon completion, to up to three email recipients.<br><br> In the Set "
250
"Schedule section, you can schedule the following three types of security "
251
"reports:<br><br> <b>Executive Security Summary:</b> A combined report, "
252
"consisting of one or more Security incident reports from one or more "
253
"machines. This report provides a single view of security events on multiple "
254
"machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that "
255
"reports which application servers are running and whether the applications "
256
"are confined by AppArmor. Application servers are applications that accept "
257
"incoming network connections. <br><br> <b>Security Incident Report:</b> A "
258
"report that displays application security for a single host. It reports "
259
"policy violations for locally confined applications during a specific time "
260
"period. You can edit and customize this report, or add new versions."
262
"The summary of scheduled reports page shows us when reports are scheduled to "
263
"run. Reports can be set to run monthly, weekly, daily, or hourly. The "
264
"default settings are daily at midnight. The reports can also be emailed, "
265
"upon completion, to up to three email recipients.<br><br> In the Set "
266
"Schedule section, you can schedule the following three types of security "
267
"reports:<br><br> <b>Executive Security Summary:</b> A combined report, "
268
"consisting of one or more Security incident reports from one or more "
269
"machines. This report provides a single view of security events on multiple "
270
"machines.<br><br> <b>Applications Audit Report:</b> An auditing tool that "
271
"reports which application servers are running and whether the applications "
272
"are confined by AppArmor. Application servers are applications that accept "
273
"incoming network connections. <br><br> <b>Security Incident Report:</b> A "
274
"report that displays application security for a single host. It reports "
275
"policy violations for locally confined applications during a specific time "
276
"period. You can edit and customize this report, or add new versions."
278
#: report_helptext.ycp:15
280
" The View Archive Reports form enables you to view previously generated "
281
"reports, located in the /var/log/apparmor/reports-archived directory. The "
282
"checkboxes at the top of the form enable you to narrow-down the category of "
283
"reports shown in the list to the following: SIR Reports, AUD Reports, or ESS "
284
"Reports. To see report details, select a report and click the <b>View</b> "
285
"button.<br><br> You can view reports from one or more systems if you move "
286
"the reports to the /var/log/apparmor/reports-archived directory."
288
" The View Archive Reports form enables you to view previously generated "
289
"reports, located in the /var/log/apparmor/reports-archived directory. The "
290
"checkboxes at the top of the form enable you to narrow-down the category of "
291
"reports shown in the list to the following: SIR Reports, AUD Reports, or ESS "
292
"Reports. To see report details, select a report and click the <b>View</b> "
293
"button.<br><br> You can view reports from one or more systems if you move "
294
"the reports to the /var/log/apparmor/reports-archived directory."
296
#: report_helptext.ycp:27
300
#: report_helptext.ycp:28
302
"<b>Security Incident Report (SIR):</b> A report that displays security "
303
"events of interest to an administrator. The SIR reports policy violations "
304
"for locally confined applications during the specified time period. The SIR "
305
"reports policy exceptions and policy engine state changes. These two types "
306
"of security events are defined as follows: <ul> <li><b>Policy Exceptions:</"
307
"b> When an application requests a resource that's not defined within its "
308
"profile, a security event is generated. <li><b>Policy Engine State Changes:"
309
"</b> Enforces policy for applications and maintains its own state, including "
310
"when engines start or stop, when a policy is reloaded, and when global "
311
"security feature are enabled or disabled. </ul> Select the report from the "
312
"archive, then <b>View</b> to see the report details."
314
"<b>Security Incident Report (SIR):</b> A report that displays security "
315
"events of interest to an administrator. The SIR reports policy violations "
316
"for locally confined applications during the specified time period. The SIR "
317
"reports policy exceptions and policy engine state changes. These two types "
318
"of security events are defined as follows: <ul> <li><b>Policy Exceptions:</"
319
"b> When an application requests a resource that's not defined within its "
320
"profile, a security event is generated. <li><b>Policy Engine State Changes:"
321
"</b> Enforces policy for applications and maintains its own state, including "
322
"when engines start or stop, when a policy is reloaded, and when global "
323
"security feature are enabled or disabled. </ul> Select the report from the "
324
"archive, then <b>View</b> to see the report details."
326
#: report_helptext.ycp:31
328
"<b>Applications Audit Report (AUD):</b> An auditing tool that reports which "
329
"application servers are running and whether they are confined by AppArmor. "
330
"Application servers are applications that accept incoming network "
331
"connections. This report provides the host machine's IP Address, the date "
332
"the Applications Audit Report ran, the name and path of the unconfined "
333
"program or application server, the suggested profile or a placeholder for a "
334
"profile for an unconfined program, the process ID number, The state of the "
335
"program (confined or unconfined), and the type of confinement that the "
336
"profile is performing (enforce/complain).<br><br> "
338
"<b>Applications Audit Report (AUD):</b> An auditing tool that reports which "
339
"application servers are running and whether they are confined by AppArmor. "
340
"Application servers are applications that accept incoming network "
341
"connections. This report provides the host machine's IP Address, the date "
342
"the Applications Audit Report ran, the name and path of the unconfined "
343
"program or application server, the suggested profile or a placeholder for a "
344
"profile for an unconfined program, the process ID number, The state of the "
345
"program (confined or unconfined), and the type of confinement that the "
346
"profile is performing (enforce/complain).<br><br> "
348
#: report_helptext.ycp:33
350
"<b>Executive Security Summary (ESS):</b> A combined report, consisting of "
351
"one or more high-level reports from one or more machines. This report can "
352
"provide a single view of security events on multiple machines if each "
353
"machine's data is copied to the reports archive directory, which is <b>/var/"
354
"log/apparmor/reports-archived</b>. This report provides the host machine's "
355
"IP address, the start and end dates of the polled events, total number of "
356
"rejects, total number of events, average of severity levels reported, and "
357
"the highest severity level reported. One line of the ESS report represents a "
358
"range of SIR reports.<br><br> "
360
"<b>Executive Security Summary (ESS):</b> A combined report, consisting of "
361
"one or more high-level reports from one or more machines. This report can "
362
"provide a single view of security events on multiple machines if each "
363
"machine's data is copied to the reports archive directory, which is <b>/var/"
364
"log/apparmor/reports-archived</b>. This report provides the host machine's "
365
"IP address, the start and end dates of the polled events, total number of "
366
"rejects, total number of events, average of severity levels reported, and "
367
"the highest severity level reported. One line of the ESS report represents a "
368
"range of SIR reports.<br><br> "
370
#: reporting_archived_dialogs.ycp:37
371
msgid "Archived Security Incident Report - Page "
372
msgstr "Archived Security Incident Report - Page "
374
#: reporting_archived_dialogs.ycp:37 reporting_dialogues.ycp:414
375
#: reporting_dialogues.ycp:968 reporting_dialogues.ycp:971
379
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:426
380
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
381
#: reporting_dialogues.ycp:975 reporting_dialogues.ycp:985
385
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:426
386
#: reporting_dialogues.ycp:673 reporting_dialogues.ycp:803
387
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
388
#: reporting_dialogues.ycp:975
392
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:426
393
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
394
#: reporting_dialogues.ycp:975
398
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:427
399
#: reporting_dialogues.ycp:673 reporting_dialogues.ycp:969
400
#: reporting_dialogues.ycp:972 reporting_dialogues.ycp:976
404
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:427
405
#: reporting_dialogues.ycp:673 reporting_dialogues.ycp:969
406
#: reporting_dialogues.ycp:972 reporting_dialogues.ycp:976
410
#: reporting_archived_dialogs.ycp:47 reporting_archived_dialogs.ycp:105
411
#: reporting_dialogues.ycp:189 reporting_dialogues.ycp:226
412
#: reporting_dialogues.ycp:272 reporting_dialogues.ycp:427
413
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972 sd-config.ycp:261
414
#: sd-config.ycp:274 sd-config.ycp:287
418
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:427
419
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
423
#: reporting_archived_dialogs.ycp:47 reporting_archived_dialogs.ycp:111
424
#: reporting_dialogues.ycp:183 reporting_dialogues.ycp:220
425
#: reporting_dialogues.ycp:278 reporting_dialogues.ycp:427
426
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
430
#: reporting_archived_dialogs.ycp:47 reporting_dialogues.ycp:427
431
#: reporting_dialogues.ycp:969 reporting_dialogues.ycp:972
435
#: reporting_archived_dialogs.ycp:53
439
#: reporting_archived_dialogs.ycp:54 reporting_dialogues.ycp:1005
443
#: reporting_archived_dialogs.ycp:55
447
#: reporting_archived_dialogs.ycp:56 reporting_dialogues.ycp:1007
451
#: reporting_archived_dialogs.ycp:57
455
#: reporting_archived_dialogs.ycp:75 reporting_dialogues.ycp:243
456
msgid "Filter By Date Range"
457
msgstr "Filter By Date Range"
459
#: reporting_archived_dialogs.ycp:76 reporting_dialogues.ycp:244
460
msgid " Select Date Range "
461
msgstr " Select Date Range "
463
#: reporting_archived_dialogs.ycp:78 reporting_dialogues.ycp:246
464
msgid "Enter Starting Date/Time"
465
msgstr "Enter Starting Date/Time"
467
#: reporting_archived_dialogs.ycp:81 reporting_archived_dialogs.ycp:91
468
#: reporting_dialogues.ycp:249 reporting_dialogues.ycp:259
472
#: reporting_archived_dialogs.ycp:82 reporting_archived_dialogs.ycp:92
473
#: reporting_dialogues.ycp:250 reporting_dialogues.ycp:260
477
#: reporting_archived_dialogs.ycp:83 reporting_archived_dialogs.ycp:93
478
#: reporting_dialogues.ycp:251 reporting_dialogues.ycp:261
482
#: reporting_archived_dialogs.ycp:84 reporting_archived_dialogs.ycp:94
483
#: reporting_dialogues.ycp:252 reporting_dialogues.ycp:262
487
#: reporting_archived_dialogs.ycp:85 reporting_archived_dialogs.ycp:95
488
#: reporting_dialogues.ycp:253 reporting_dialogues.ycp:263
492
#: reporting_archived_dialogs.ycp:88 reporting_dialogues.ycp:256
493
msgid "Enter Ending Date"
494
msgstr "Enter Ending Date"
496
#: reporting_archived_dialogs.ycp:101 reporting_dialogues.ycp:176
497
#: reporting_dialogues.ycp:213 reporting_dialogues.ycp:268
498
#: reporting_dialogues.ycp:485
500
msgstr "Program name"
502
#: reporting_archived_dialogs.ycp:102 reporting_dialogues.ycp:177
503
#: reporting_dialogues.ycp:214 reporting_dialogues.ycp:269
505
msgstr "Profile name"
507
#: reporting_archived_dialogs.ycp:103 reporting_dialogues.ycp:182
508
#: reporting_dialogues.ycp:219 reporting_dialogues.ycp:270
512
#: reporting_archived_dialogs.ycp:106 reporting_dialogues.ycp:17
513
#: reporting_dialogues.ycp:56 reporting_dialogues.ycp:69
514
#: reporting_dialogues.ycp:70 reporting_dialogues.ycp:190
515
#: reporting_dialogues.ycp:227 reporting_dialogues.ycp:273
516
#: reporting_dialogues.ycp:829 reporting_dialogues.ycp:834
517
#: reporting_dialogues.ycp:1548 reporting_dialogues.ycp:1576
518
#: reporting_dialogues.ycp:1626 reporting_dialogues.ycp:1627
519
#: reporting_dialogues.ycp:1628 reporting_dialogues.ycp:1657
520
#: reporting_dialogues.ycp:1658 reporting_dialogues.ycp:1726
521
#: reporting_dialogues.ycp:1913 reporting_dialogues.ycp:1928
522
#: reporting_dialogues.ycp:1974 reporting_dialogues.ycp:1983
523
#: reporting_dialogues.ycp:1987 reporting_dialogues.ycp:2001
524
#: reporting_dialogues.ycp:2002 reporting_dialogues.ycp:2003
525
#: reporting_utils.ycp:195 reporting_utils.ycp:341
529
#: reporting_archived_dialogs.ycp:106 reporting_dialogues.ycp:273
533
#: reporting_archived_dialogs.ycp:112 reporting_dialogues.ycp:229
534
#: reporting_dialogues.ycp:279
535
msgid "Access Type: R"
536
msgstr "Access Type: R"
538
#: reporting_archived_dialogs.ycp:113 reporting_dialogues.ycp:230
539
#: reporting_dialogues.ycp:280
543
#: reporting_archived_dialogs.ycp:120 reporting_dialogues.ycp:288
544
#: reporting_dialogues.ycp:379 reporting_dialogues.ycp:1592
545
#: reporting_dialogues.ycp:1952
549
#: reporting_archived_dialogs.ycp:121 reporting_dialogues.ycp:289
550
#: reporting_dialogues.ycp:380 reporting_dialogues.ycp:1991
554
#: reporting_archived_dialogs.ycp:121 reporting_dialogues.ycp:289
555
#: reporting_dialogues.ycp:380
559
#: reporting_archived_dialogs.ycp:121 reporting_dialogues.ycp:289
560
#: reporting_dialogues.ycp:380
564
#: reporting_archived_dialogs.ycp:121 reporting_dialogues.ycp:289
565
#: reporting_dialogues.ycp:380
569
#: reporting_archived_dialogs.ycp:123 reporting_dialogues.ycp:291
570
#: reporting_dialogues.ycp:382 reporting_dialogues.ycp:1595
571
#: reporting_dialogues.ycp:1955
572
msgid "Location to store log."
573
msgstr "Location to store log."
575
#: reporting_archived_dialogs.ycp:124 reporting_dialogues.ycp:292
576
#: reporting_dialogues.ycp:383 reporting_dialogues.ycp:797
577
#: reporting_dialogues.ycp:1596 reporting_dialogues.ycp:1956
581
#: reporting_archived_dialogs.ycp:125 reporting_dialogues.ycp:293
582
#: reporting_dialogues.ycp:384 reporting_dialogues.ycp:798
583
#: reporting_dialogues.ycp:1597 reporting_dialogues.ycp:1957
587
#: reporting_archived_dialogs.ycp:145 reporting_dialogues.ycp:497
588
#: reporting_dialogues.ycp:831
589
msgid "Report Configuration Dialog"
590
msgstr "Report Configuration Dialog"
592
#: reporting_archived_dialogs.ycp:145 reporting_dialogues.ycp:724
593
#: reporting_dialogues.ycp:832 reporting_dialogues.ycp:1038
594
#: reporting_dialogues.ycp:1108 reporting_dialogues.ycp:1120
595
#: reporting_dialogues.ycp:1132 reporting_dialogues.ycp:1183
596
#: reporting_dialogues.ycp:1209 reporting_dialogues.ycp:1232
597
#: reporting_dialogues.ycp:1248 reporting_dialogues.ycp:1263
598
#: reporting_dialogues.ycp:1271 reporting_dialogues.ycp:1280
599
#: reporting_dialogues.ycp:1288 reporting_dialogues.ycp:1295
600
#: reporting_dialogues.ycp:1412 reporting_dialogues.ycp:1448
601
#: reporting_dialogues.ycp:1466 reporting_dialogues.ycp:1476
602
#: reporting_dialogues.ycp:1483 reporting_dialogues.ycp:1491
603
#: reporting_dialogues.ycp:1499 reporting_dialogues.ycp:2212
604
#: reporting_dialogues.ycp:2262
608
#: reporting_archived_dialogs.ycp:145 reporting_dialogues.ycp:497
609
#: reporting_dialogues.ycp:724 reporting_dialogues.ycp:832
610
#: reporting_dialogues.ycp:1608 reporting_dialogues.ycp:2212
611
#: reporting_dialogues.ycp:2262
615
#: reporting_archived_dialogs.ycp:196 reporting_archived_dialogs.ycp:211
616
msgid "February only has 28 days! Fixing."
617
msgstr "February only has 28 days! Fixing."
619
#: reporting_archived_dialogs.ycp:199
620
msgid "February only has 29 days! Fixing."
621
msgstr "February only has 29 days! Fixing."
623
#: reporting_archived_dialogs.ycp:203 reporting_archived_dialogs.ycp:222
624
msgid "Month only has 30 days! Fixing."
625
msgstr "Month only has 30 days! Fixing."
627
#: reporting_archived_dialogs.ycp:216
628
msgid "February only has 29 days!"
629
msgstr "February only has 29 days!"
631
#: reporting_dialogues.ycp:145
632
msgid "Unrecognized form request."
633
msgstr "Unrecognized form request."
635
#: reporting_dialogues.ycp:193 reporting_dialogues.ycp:881
636
#: reporting_dialogues.ycp:1699 reporting_dialogues.ycp:2033
637
msgid "Access Type: "
638
msgstr "Access Type: "
640
#: reporting_dialogues.ycp:195 reporting_dialogues.ycp:890
641
#: reporting_dialogues.ycp:1708 reporting_dialogues.ycp:2041
645
#: reporting_dialogues.ycp:200 reporting_dialogues.ycp:235
646
#: reporting_dialogues.ycp:1607 reporting_dialogues.ycp:1884
647
#: reporting_dialogues.ycp:1894 reporting_dialogues.ycp:2143
651
#: reporting_dialogues.ycp:201 reporting_dialogues.ycp:236
652
#: reporting_dialogues.ycp:1895 reporting_utils.ycp:68 reporting_utils.ycp:131
653
#: reporting_utils.ycp:203 reporting_utils.ycp:348
657
#: reporting_dialogues.ycp:414 reporting_dialogues.ycp:968
658
msgid "On Demand Event Report - Page "
659
msgstr "On Demand Event Report - Page "
661
#: reporting_dialogues.ycp:483
662
msgid "Filter By Program Name"
663
msgstr "Filter By Program Name"
665
#: reporting_dialogues.ycp:489
666
msgid "Export Report"
667
msgstr "Export Report"
669
#: reporting_dialogues.ycp:491
670
msgid "Export File Location"
671
msgstr "Export File Location"
673
#: reporting_dialogues.ycp:492
674
msgid "Select Export Format"
675
msgstr "Select Export Format"
677
#: reporting_dialogues.ycp:493
681
#: reporting_dialogues.ycp:494
685
#: reporting_dialogues.ycp:663
687
"<b>AppArmor Security Events</b><p>\n"
688
" This table displays the events found that match your "
691
"<b>AppArmor Security Events</b><p>\n"
692
" This table displays the events found that match your "
695
#: reporting_dialogues.ycp:670
696
msgid "AppArmor Event Report Data"
697
msgstr "AppArmor Event Report Data"
699
#: reporting_dialogues.ycp:673
700
msgid "AppArmor Message"
701
msgstr "AppArmor Message"
703
#: reporting_dialogues.ycp:677 reporting_dialogues.ycp:724
704
#: reporting_dialogues.ycp:1038 reporting_dialogues.ycp:1065
705
#: reporting_dialogues.ycp:1073 reporting_dialogues.ycp:1089
706
#: reporting_dialogues.ycp:2212 reporting_dialogues.ycp:2262
707
msgid "AppArmor Security Event Report"
708
msgstr "AppArmor Security Event Report"
710
#: reporting_dialogues.ycp:713
711
msgid "AppArmor Reporting"
712
msgstr "AppArmor Reporting"
714
#: reporting_dialogues.ycp:717 reporting_dialogues.ycp:2241
715
msgid "Schedule Reports"
716
msgstr "Schedule Reports"
718
#: reporting_dialogues.ycp:718 reporting_dialogues.ycp:784
719
msgid "View Archived Reports"
720
msgstr "View Archived Reports"
722
#: reporting_dialogues.ycp:719
726
#: reporting_dialogues.ycp:788
730
#: reporting_dialogues.ycp:789
734
#: reporting_dialogues.ycp:790
738
#: reporting_dialogues.ycp:796
739
msgid "Location of Archived Reports"
740
msgstr "Location of Archived Reports"
742
#: reporting_dialogues.ycp:803
746
#: reporting_dialogues.ycp:808
750
#: reporting_dialogues.ycp:809
754
#: reporting_dialogues.ycp:971
755
msgid "Archived Event Report - Page "
756
msgstr "Archived Event Report - Page "
758
#: reporting_dialogues.ycp:974 reporting_dialogues.ycp:1209
759
msgid "Applications Audit Report"
760
msgstr "Applications Audit Report"
762
#: reporting_dialogues.ycp:976
766
#: reporting_dialogues.ycp:976
770
#: reporting_dialogues.ycp:979 reporting_dialogues.ycp:984
771
msgid "Executive Security Summary"
772
msgstr "Executive Security Summary"
774
#: reporting_dialogues.ycp:980
775
msgid "Query Results"
776
msgstr "Query Results"
778
#: reporting_dialogues.ycp:980
779
msgid "No event information exists."
780
msgstr "No event information exists."
782
#: reporting_dialogues.ycp:985
786
#: reporting_dialogues.ycp:986
790
#: reporting_dialogues.ycp:986
794
#: reporting_dialogues.ycp:986
798
#: reporting_dialogues.ycp:986
802
#: reporting_dialogues.ycp:986
806
#: reporting_dialogues.ycp:1004
810
#: reporting_dialogues.ycp:1008
814
#: reporting_dialogues.ycp:1009
818
#: reporting_dialogues.ycp:1018
819
msgid "Events DB Not Initialized."
820
msgstr "Events DB not initialized."
822
#: reporting_dialogues.ycp:1028
823
msgid "The events database has not been populated. No records exist."
824
msgstr "The events database has not been populated. No records exist."
826
#: reporting_dialogues.ycp:1108
827
msgid "View Archived SIR Report"
828
msgstr "View Archived SIR Report"
830
#: reporting_dialogues.ycp:1119
831
msgid "View Archived AUD Report"
832
msgstr "View Archived AUD Report"
834
#: reporting_dialogues.ycp:1131
835
msgid "View Archived ESS Report"
836
msgstr "View Archived ESS Report"
838
#: reporting_dialogues.ycp:1183
839
msgid "Security Incident Report"
840
msgstr "Security Incident Report"
842
#: reporting_dialogues.ycp:1232
843
msgid "Executive Security Summary Report"
844
msgstr "Executive Security Summary Report"
846
#: reporting_dialogues.ycp:1236
847
msgid "No recognized report type selected. Try again."
848
msgstr "No recognized report type selected. Try again."
850
#: reporting_dialogues.ycp:1248 reporting_dialogues.ycp:1263
851
#: reporting_dialogues.ycp:1271 reporting_dialogues.ycp:1280
852
#: reporting_dialogues.ycp:1288 reporting_dialogues.ycp:1295
853
msgid "AppArmor Report"
854
msgstr "AppArmor Report"
856
#: reporting_dialogues.ycp:1412
857
msgid "AppArmor On-Demand Report"
858
msgstr "AppArmor On-Demand Report"
860
#: reporting_dialogues.ycp:1447 reporting_dialogues.ycp:1465
861
#: reporting_dialogues.ycp:1475 reporting_dialogues.ycp:1482
862
#: reporting_dialogues.ycp:1491 reporting_dialogues.ycp:1499
863
msgid "AppArmor - Run Reports"
864
msgstr "AppArmor - Run Reports"
866
#: reporting_dialogues.ycp:1547 reporting_dialogues.ycp:2197
867
#: reporting_dialogues.ycp:2248
869
msgstr "Day of Month"
871
#: reporting_dialogues.ycp:1575 reporting_dialogues.ycp:1927
872
#: reporting_dialogues.ycp:2197 reporting_dialogues.ycp:2248
876
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
880
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
884
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
888
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
892
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
896
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
900
#: reporting_dialogues.ycp:1576 reporting_dialogues.ycp:1928
904
#: reporting_dialogues.ycp:1578 reporting_dialogues.ycp:1937
905
#: reporting_dialogues.ycp:2197 reporting_dialogues.ycp:2248
909
#: reporting_dialogues.ycp:1579 reporting_dialogues.ycp:1938
913
#: reporting_dialogues.ycp:1584 reporting_dialogues.ycp:1943
914
msgid "Email Target 1"
915
msgstr "Email Target 1"
917
#: reporting_dialogues.ycp:1585 reporting_dialogues.ycp:1944
918
msgid "Email Target 2"
919
msgstr "Email Target 2"
921
#: reporting_dialogues.ycp:1586 reporting_dialogues.ycp:1945
922
msgid "Email Target 3"
923
msgstr "Email Target 3"
925
#: reporting_dialogues.ycp:1675
926
msgid "Only one contiguous space allowed in report names."
927
msgstr "Only one contiguous space allowed in report names."
929
#: reporting_dialogues.ycp:1677
931
"These characters are not allowed in report names: \"`~!@#$%^&*()[{]};:'\","
934
"These characters are not allowed in report names: \"`~!@#$%^&*()[{]};:'\","
937
#: reporting_dialogues.ycp:1679
938
msgid "Only 128 characters are allowed in report names."
939
msgstr "Only 128 characters are allowed in report names."
941
#: reporting_dialogues.ycp:1681
942
msgid "You must enter a name for the report."
943
msgstr "You must enter a name for the report."
945
#: reporting_dialogues.ycp:1683
946
msgid "You must enter at least one email address."
947
msgstr "You must enter at least one email address."
949
#: reporting_dialogues.ycp:1689
950
msgid "Each report name should be unique."
951
msgstr "Each report name should be unique."
953
#: reporting_dialogues.ycp:1885
957
#: reporting_dialogues.ycp:1905
961
#: reporting_dialogues.ycp:1905
965
#: reporting_dialogues.ycp:1975
969
#: reporting_dialogues.ycp:2014 reporting_dialogues.ycp:2093
970
msgid "You must enter at least one email address ."
971
msgstr "You must enter at least one email address ."
973
#: reporting_dialogues.ycp:2108
977
#: reporting_dialogues.ycp:2135
978
msgid "Delete Confirmation"
979
msgstr "Delete Confirmation"
981
#: reporting_dialogues.ycp:2139
982
msgid "Are you sure you want to delete: "
983
msgstr "Are you sure you want to delete: "
985
#: reporting_dialogues.ycp:2139
989
#: reporting_dialogues.ycp:2144
993
#: reporting_dialogues.ycp:2156
994
msgid "The specified directory does not exist."
995
msgstr "The specified directory does not exist."
997
#: reporting_dialogues.ycp:2197 reporting_dialogues.ycp:2248
1001
#: reporting_dialogues.ycp:2197 reporting_dialogues.ycp:2248
1005
#: reporting_dialogues.ycp:2202 reporting_dialogues.ycp:2252
1006
msgid "View Archive"
1007
msgstr "View Archive"
1009
#: reporting_dialogues.ycp:2203 reporting_dialogues.ycp:2253
1013
#: reporting_dialogues.ycp:2206 reporting_dialogues.ycp:2256
1017
#: reporting_dialogues.ycp:2207 reporting_dialogues.ycp:2257
1021
#: reporting_dialogues.ycp:2208 reporting_dialogues.ycp:2258
1025
#: reporting_dialogues.ycp:2306
1026
msgid "Cannot delete a stock report."
1027
msgstr "Cannot delete a stock report."
1029
#: reporting_utils.ycp:55
1030
msgid "No name provided for retrieving SIR report page count."
1031
msgstr "No name provided for retrieving SIR report page count."
1033
#: reporting_utils.ycp:64
1034
msgid "Enter a Page to Move to."
1035
msgstr "Enter a Page to Move to."
1037
#: reporting_utils.ycp:67 reporting_utils.ycp:130 reporting_utils.ycp:202
1038
#: reporting_utils.ycp:347
1042
#: reporting_utils.ycp:196
1046
#: reporting_utils.ycp:197
1050
#: reporting_utils.ycp:198
1054
#: reporting_utils.ycp:199
1058
#: reporting_utils.ycp:342
1062
#: reporting_utils.ycp:343
1066
#: reporting_utils.ycp:344
1071
msgid "AppArmor is disabled"
1072
msgstr "AppArmor is disabled"
1075
msgid "AppArmor is enabled"
1076
msgstr "AppArmor is enabled"
1079
msgid "Notification is disabled"
1080
msgstr "Notification is disabled"
1083
msgid "Notification is enabled"
1084
msgstr "Notification is enabled"
1087
msgid "AppArmor Configuration"
1088
msgstr "AppArmor Configuration"
1092
"<p><b>AppArmor Status</b><br>This reports whether the AppArmor policy "
1093
"enforcement module is loaded and functioning.</p> <p><b>Security Event "
1094
"Notification</b><br>When an access violation occurs, configure this tool if "
1095
"you want to be notified via email. </p>"
1099
msgid "AppArmor Status"
1100
msgstr "AppArmor Status"
1103
msgid "Enable AppArmor"
1104
msgstr "Enable AppArmor"
1106
#: sd-config.ycp:51 sd-config.ycp:66
1111
msgid "Enable Security Event Notification"
1112
msgstr "Enable Security Event Notification"
1114
#: sd-config.ycp:215 sd-config.ycp:227 sd-config.ycp:239
1118
#: sd-config.ycp:216 sd-config.ycp:228 sd-config.ycp:240
1122
#: sd-config.ycp:217 sd-config.ycp:229 sd-config.ycp:241
1126
#: sd-config.ycp:218 sd-config.ycp:230 sd-config.ycp:242
1130
#: sd-config.ycp:219 sd-config.ycp:231 sd-config.ycp:243
1134
#: sd-config.ycp:220 sd-config.ycp:232 sd-config.ycp:244
1138
#: sd-config.ycp:221 sd-config.ycp:233 sd-config.ycp:245
1142
#: sd-config.ycp:222 sd-config.ycp:234 sd-config.ycp:246
1146
#: sd-config.ycp:223 sd-config.ycp:235 sd-config.ycp:247
1150
#: sd-config.ycp:259 sd-config.ycp:272 sd-config.ycp:285
1154
#: sd-config.ycp:260 sd-config.ycp:273 sd-config.ycp:286
1155
msgid "Email Address"
1156
msgstr "Email Address"
1158
#: sd-config.ycp:264 sd-config.ycp:277 sd-config.ycp:290
1159
msgid "Include Unknown Severity Events"
1160
msgstr "Include Unknown Severity Events"
1162
#: sd-config.ycp:303
1163
msgid "Security Event Notification"
1164
msgstr "Security Event Notification"
1166
#: sd-config.ycp:303