CSSCurrent en:Configuration of Connectors

Aus Cryptshare Documentation
Version vom 28. September 2022, 13:59 Uhr von imported>Frorathm
(Unterschied) ← Nächstältere Version | Aktuelle Version (Unterschied) | Nächstjüngere Version → (Unterschied)
Wechseln zu:Navigation, Suche



Archiving Connector Configuration

Common Settings

Except from the Legacy Connector all archiving connectors share the following settings.

  • The target directory
  • A 'write' suffix
  • A 'ready' suffix
  • An 'archived' suffix

File Name Suffixes

Some archiving systems support file name suffixes. This way files can be marked so that the corresponding system knows when a file is ready for access or ready for deletion.

Setting Purpose Example
Target Directory The target directory to which archiving information will be written. C:\\cryptshare3\_archive\\
Write Suffix This file name suffix is used when Cryptshare is currently writing new files for archiving. Archiving systems can check for this suffix in order to determine if they can access the file already or not. A transfer is made containing the file 'secret\_document.docx'.

While writing the file to the archiving directory the file name is 'secret\_document.docx.myWriteSuffix'.

Ready Suffix This file name suffix is used When Cryptshare has finished writing a file for archiving and it is ready for the archiving system. The archiving system can now process this file. A transfer was made containing the file 'secret\_document.docx'.

The archiving system will process the file as soon as it is named 'secret\_document.docx.myReadySuffix'

Archived Suffix This file name suffix is set by the archiving system. If a file has been marked this way Cryptshare will remove this file again during the next cleanup cycle. A transfer was made containing the file 'secret\_document.docx'.

The archiving system has archived the file and renames it to 'secret\_document.docx.myArchivedSuffix'. Cryptshare removes the file from the target directory during the next cleanup cycle.

Please note that Cryptshare will only delete archived files in case they have been marked with the 'archived'-suffix.


Secure Copy Settings

In contrast to the other connectors the SCP connector has additional settings.

Please note, that SCP can only work if the remote host is configured as SCP server. This is usually the case for linux hosts.

Host Configuration

Defines the remote host to which the archiving connector will establish a connection to. You can either enter an ip-address or the name of the host. The default port for the scp protocol is port 22 which should be enabled in your firewall configuration.

Known Hosts

SCP is working based on the SSH protocol. When establishing a connection to an unknown remote host, this host can be identified by a so called 'fingerprint'. In order to allow the scp connector establishing future connections to this remote host, this fingerprint needs to be imported first. You can add this fingerprint manually if you already know it, or you can use the import feature which will show up as soon as you click on the 'Test Connection' button and a connection is successfully established.

Archiving with an SCP connector will fail if the fingerprint of the remote host has not been imported or manually entered.

Authentication Methods

The SCP connector allows two authentication methods. A standard password authentication or a public-key authentication method. Most SCP servers have setup the password authentication method.

In order to use public key authentication you need to setup your SCP server first. Please refer to our Cryptshare Knowledgebase for detailed instructions.

File Name Sanitization 

When files are saved to the disk during archiving with a name that is not a valid filename, it will be sanitized. This means that special characters are replaced with underscores, and the filename will be limited to 200 characters, excluding the archiving suffix, if it is too long. When multiple files with the same name exist, a numeric counter will be appended before the file extension (e.g. "foo.txt" becomes "foo1.txt").