Roxen.git / server / translations / ces / admin_tasks.xml

version» Context lines:

Roxen.git/server/translations/ces/admin_tasks.xml:1:   <?xml version="1.0" encoding="iso-8859-2"?>   <locale version="1.0"/>   <project>admin_tasks</project>   <language>ces</language>   <file>../base_server/roxen.pike</file>   <file>../config_interface/actions/cachestatus.pike</file> + <file>../config_interface/actions/change_version.pike</file>   <file>../config_interface/actions/debug_info.pike</file>   <file>../config_interface/actions/feature_list.pike</file>   <file>../config_interface/actions/flush.pike</file>   <file>../config_interface/actions/ftpstatus.pike</file>   <file>../config_interface/actions/generate_rsa.pike</file>   <file>../config_interface/actions/listfonts.pike</file>   <file>../config_interface/actions/locks.pike</file>   <file>../config_interface/actions/make_rsa_csr.pike</file>   <file>../config_interface/actions/make_selfsigned_dsa.pike</file>   <file>../config_interface/actions/make_selfsigned_rsa.pike</file>
Roxen.git/server/translations/ces/admin_tasks.xml:575:   <o>Credentials:</o>   <t></t>   </str>      <str id="84">   <new/>   <o>Current working directory:</o>   <t></t>   </str>    - <str id="87"> - <new/> - <o>In order to use the SSL on your server, you first have to create a random RSA key pair. One part of the key is kept secret. </o> - <t></t> - </str> +     -  +    <str id="88">   <new/>   <o>The other part should be submitted to a certificate authority, such as Thawte or VeriSign. The certificate authority will return the signed certificate that need to run a secure server.</o>   <t></t>   </str>      <str id="89">   <new/>   <o>The other part is used to create a certificate. You can create a certificate yourself; this is not the recommended way to use SSL, and browsers will complain about not recognizing the entity that has signed the key (i.e. you). But a self-signed certificate is a lot better than nothing.</o>   <t></t>
Roxen.git/server/translations/ces/admin_tasks.xml:625:   </str>      <str id="94">   <new/>   <o>Key size</o>   <t></t>   </str>      <str id="95">   <new/> - <o>The largest RSA key that is publicly known to have been broken was 155 decimal digits, or 512 bits large. This effort required approximately 8000 MIPS-years.&lt;p&gt;A key 1024 bits large should be secure enough for most applications, but of course you can you use an even larger key if you so wish.</o> + <o>The largest key that is publicly known to have been broken was 155 decimal digits, or 512 bits large. This effort required approximately 8000 MIPS-years.&lt;p&gt;A key 1024 bits large should be secure enough for most applications, but of course you can you use an even larger key if you so wish.</o>   <t></t>   </str>      <str id="96">   <new/>   <o>Key file</o>   <t></t>   </str>      <str id="97">
Roxen.git/server/translations/ces/admin_tasks.xml:869:   <new/>   <o>Generate an DSA key and a Self Signed Certificate...</o>   <t></t>   </str>      <str id="135">   <new/>   <o>Invalid key size.</o>   <t></t>   </str> +  + <str id="40"> + <new/> + <o>In order to use the SSL on your server, you first have to create a random key pair. One part of the key is kept secret. </o> + <t></t> + </str> +  + <str id="41"> + <new/> + <o>Change roxen version...</o> + <t></t> + </str> +  + <str id="42"> + <new/> + <o>Indeed</o> + <t></t> + </str> +  + <str id="43"> + <new/> + <o>1 month</o> + <t></t> + </str> +  + <str id="44"> + <new/> + <o>%d months</o> + <t></t> + </str> +  + <str id="45"> + <new/> + <o>%d days</o> + <t></t> + </str> +  + <str id="46"> + <new/> + <o>Change Roxen version</o> + <t></t> + </str> +  + <str id="47"> + <new/> + <o>Changing roxen version</o> + <t></t> + </str> +  + <str id="48"> + <new/> + <o>Version</o> + <t></t> + </str> +  + <str id="85"> + <new/> + <o>Release date</o> + <t></t> + </str> +  + <str id="86"> + <new/> + <o>Age</o> + <t></t> + </str> +  + <str id="136"> + <new/> + <o>Directory</o> + <t></t> + </str> +  + <str id="137"> + <new/> + <o>If you change to one these roxen versions, you will not be able to change back from the administration interface, you will instead have to edit the file %O manually, shutdown the server, and execute %O again</o> + <t></t> + </str> +  + <str id="138"> + <new/> + <o>Change version</o> + <t></t> + </str>