|Anonymous | Login | Signup for a new account||2017-06-28 09:11 CEST|
|My View | View Issues | Change Log | Roadmap | | Repositories | Search | My Account|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000825||bareos-core||[All Projects] storage daemon||public||2017-06-06 15:40||2017-06-06 15:40|
|Target Version||Fixed in Version|
|Summary||0000825: Migrate jobs (SD to SD) in TLS|
doing some network analysis I just noticed that apparently migration jobs are not TLS encrypted.
Everything else in our setup is in TLS, so I'd like to encrypt SD-to-SD traffic, too.
Am I missing something?
|Steps To Reproduce||We have 2 SD in our setup. |
SD1 backs up hosts in an isolated security zone.
SD2 backs up hosts in a more relaxed zone, AND it also pulls backups from SD1 to store them long-term on our tapes.
Ideally, the job transfers initiated by the "Migrate" type job should be encrypted (for obvious security reasons). Should I put the TLS directives in the "fake" Client? Which certs would it use?
Here is my migration setup
Name = "migrate-zoneA2zoneB"
Type = Migrate
Pool = zoneA-staging-pool0
Client = None
FileSet = None
Schedule = "WeeklyCycle-AfterBackup"
Maximum Concurrent Jobs = 4
Selection Type = Volume
Selection Pattern = "StagingFile.*"
Purge Migration Job = yes
Messages = Standard
# Fake fileset and client for migration jobs
Name = None
signature = MD5
Name = None
Address = localhost
Password = "NoNe"
Catalog = MyCatalog
|Additional Information||Sorry if this is already explained somewhere in the documentation, but I looked and could not find it.|
|Tags||No tags attached.|
|2017-06-06 15:40||renato.ramonda||New Issue|
|Copyright © 2000 - 2017 MantisBT Team|