TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


common:security_details

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
common:security_details [2017/06/23 22:03] – [GazillaByte Employees] Gerard Nicolcommon:security_details [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 8: Line 8:
  
 In addition to this, many of our employees have worked in military and law enforcement roles and have obtained the required clearances to perform these functions. In addition to this, many of our employees have worked in military and law enforcement roles and have obtained the required clearances to perform these functions.
 +
 {{:common:staff.png|}} {{:common:staff.png|}}
  
Line 48: Line 49:
  
 This protocol uses only one port (usually 5000), but can also be tunneled through a HTTPS proxy server (TapeTrack clients use an outbound connection and the server accepts inbound connections). This protocol uses only one port (usually 5000), but can also be tunneled through a HTTPS proxy server (TapeTrack clients use an outbound connection and the server accepts inbound connections).
-===== Enscryption =====+===== Encryption =====
  
 TapeTrack uses symmetric AES encryption to encrypt data and all passwords are hashed and stored using the MD5 algorithm. TapeTrack uses symmetric AES encryption to encrypt data and all passwords are hashed and stored using the MD5 algorithm.
common/security_details.1498255411.txt.gz · Last modified: 2025/01/21 22:07 (external edit)