Menu: attitudes(settings) / Local servers / user / to password

User's names and password for DFÜ-network and Skripte:

Here the user's names and password can be fixed for Skripte and for the network-connections DFÜ. Besides, the password and user's name for the network-connections DFÜ are only required if the hamster should produce the connection. See the also starting Moreover of the DFÜ-network about menu and the script order-HamRasDial.

The additional password-sentences with the names " 1 $ ", " 2 $ "... Are determined for the script processing and usable apart from that not meaningfully.

The maximum number the password provided for Skripte is adjustable in the field " Max Skript PW ". The standard is to 30 passwords.

The password-fields can have three conditions:

- User's name and password from asks only with necessity " {questions} " Of the hamster.

- " {Set} " The hamster stores the data in the file " passport Word.!!! " From. (See indication).

- " {Empty} " The hamster applies no authentication

In order to edit the fields the corresponding entry is to be pretended and the switch(counter) [treatment] to operate.

In order to delete of user's name and password the switch(counter) [deleting] is to be applied. Afterwards the field gets to the status " {empty} ".

By means of the folding border "PW-coding" is adjustable on the basis of which data the hamster should encode data. The less specific data flow in, the light a stolen password-file can be used by others. Moreover, a change means that all password must be given one more time - incl. the password for all servers.

Important indication to the password:

The passwords become a passport Word in the file ".!!! " Stored. Never leave this file to other persons, also then not if you have problems with their(her) accesses or similar problems!

The entries in the file " passport Word.!!! " Are encoded with the "Blowfish" algorithm. The kryptografische key applied for it contains - according to attitude(setting) mentioned at the top - u.a. some system information (PC-name, operating system-version etc) and the Anmeldenamen.

Certainly, this complicates the use of a stolen password-file, but the general acceptance that the coding of a file coded with this algorithm 100% is sure, is wrong. However, correctly is that this procedure is essentially safer than one storage in the clear text or in with ROT13 or XOR to veiled files.

Unable to open file