Difference between revisions of "SSH Data Transfers"

From Lsdf
(Created page with "share.lsdf.kit.edu # use-cases: ## sharing "private" data with colaborators (sfp...) ## making some data public via http (for instance data referenced in a publication) This se…")
 
 
Line 1: Line 1:
 
share.lsdf.kit.edu
 
share.lsdf.kit.edu
   
# use-cases:
+
* use-cases:
## sharing "private" data with colaborators (sfp...)
+
** sharing "private" data with colaborators (sfp...)
## making some data public via http (for instance data referenced in a publication)
+
** making some data public via http (for instance data referenced in a publication)
   
 
This server is NOT sharing LSDF data directly, but:
 
This server is NOT sharing LSDF data directly, but:
   
# the server provides a second copy of the data (it is separate from the
+
* the server provides a second copy of the data (it is separate from the
 
LSDF/DDN/GPFS data). Here the idea was security -> whatever it happens, the
 
LSDF/DDN/GPFS data). Here the idea was security -> whatever it happens, the
 
original data is secure. Therefore the data would need to be transfereed
 
original data is secure. Therefore the data would need to be transfereed
 
there, disk is ~ 4TB.
 
there, disk is ~ 4TB.
   
# the access is via SFTP/SCP on port 2222 (private data,
+
* the access is via SFTP/SCP on port 2222 (private data,
 
access with username & password) or via http for public data (unprotected
 
access with username & password) or via http for public data (unprotected
 
unless you add a .htaccess file).
 
unless you add a .htaccess file).

Latest revision as of 11:26, 23 April 2013

share.lsdf.kit.edu

  • use-cases:
    • sharing "private" data with colaborators (sfp...)
    • making some data public via http (for instance data referenced in a publication)

This server is NOT sharing LSDF data directly, but:

  • the server provides a second copy of the data (it is separate from the

LSDF/DDN/GPFS data). Here the idea was security -> whatever it happens, the original data is secure. Therefore the data would need to be transfereed there, disk is ~ 4TB.

  • the access is via SFTP/SCP on port 2222 (private data,

access with username & password) or via http for public data (unprotected unless you add a .htaccess file).