yast-security/master — Hindi @ openSUSE Weblate: &Shutdown Behaviour of %s Login Manager:

Translation

English ComboBox label TRANSLATORS: %s will be the configured display manager usually: GDM or KDM, but could be XDM,WDM,ENTRANCE,CONSOLE

Hindi

Needs editing

Skip

	English	Hindi	Actions
	User on the active console	विरचयुल मशीन वातावरण तैयार नही कर सकता ।
	Anyone can hibernate
	Authentication always required	प्रमाणीकरण कुंजी
	P&assword Encryption Method	पासवर्ड इंक्रिप्सन पद्धति(&a)
	&Check New Passwords	नए पासवर्डों की जांच(&C)
	Numb&er of Passwords to Remember	याद रखने वाले पासवर्डों की संख्या(&e)
	&Minimum Acceptable Password Length	पासवर्ड की स्वीकार करने योग्य न्यूनतम लंबाई(&M)
	&Days before Password Expires Warning	पासवर्ड का समय समाप्त होने की चेतावनी से दिन पहले(&D)
	&File Permissions	&फाइल अनुमतियां
	Easy	आसान
	Secure	सुरक्षित
	Paranoid	पैरानोइड
	&User Launching updatedb	&उपयोगकर्ता updatedb लांच कर रहा है
	Ma&ximum	अ&धिकतम
	&Minimum	&न्यूनतम
	&Shutdown Behaviour of %s Login Manager:	KDM का शटडाउन व्यवहार :(&S)
	Predefined Security Configurations	पहले से बताए गए समनुरुपण
	Security	सुरक्षित
	Security Configuration	सुरक्षा विन्यास
	Initializing...	शुरू कर रहा हैं ....
	Security Policies	सुरक्षा व्यवस्था
	&Security Policies	सुरक्षा व्यवस्था
	The current configuration does not comply with the enabled security policies.
	<p><b>Security Policies</b</p> <p>This section allows to configure the installed system to conform with the guidelines of a given security policy like the Security Technical Implementation Guide (STIG) of the Defense Information Systems Agency (DISA).</p> <p>Enabling a policy allows to configure the new system to execute a full security scan using the OpenSCAP tools in the first boot. By default, that will generate a report at <tt>/var/log/ssg-apply/</tt> listing the rules that would need some kind of remediation. The system can also be configured to automatically apply remediations right after the initial scan. Note that may lead to a system that is secure to the point of being unusable for some use cases. It is also possible to completely skip the automatic scan.</p> <p>Enabling a security policy will also cause the installer to check some rules that can hardly be remediated after installation. For each failing rule the installer will display several well-known identifiers and a link to the functionality of the installer that can be used to manually remediate the issue before installing.<p>
	%{policy} is enabled (<a href="%{link}">disable</a>)
	%{policy} is disabled (<a href="%{link}">enable</a>)
	The following rules were already checked by the installer and are failing:
	The following rules are disabled:
	No SCAP scan will be performed on first boot
	A full SCAP scan will be performed on first boot
	A full SCAP remediation will be performed on first boot