User story #7986: Make copying the tools encrypted again - Rudder - Issue Tracker

Actions

Copy link

User story #7986

closed

User story #6363: Secure agent/server communication

Make copying the tools encrypted again

Added by Janos Mattyasovszky over 8 years ago. Updated almost 7 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

Benoît PECCATTE

Category:

System techniques

Target version:

4.1.10

Pull Request:

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

Description

From a point of security it would be recommended to also encrypt the copy-progress of the tools.

This was changed in #7644 by:
https://github.com/Normation/rudder-techniques/commit/924bde1d#diff-54497584de9934e14ae1d1d338b27e04L79

Regarding it being open-source: It would theoretically allow examination of which version of tools the whole environment is using just by examining the network traffic by MITM, use that to determine which version of rudder you are using, and with that information find a vulnerability, that could serve as an attack vector.

It would make more sense to just create a different copy_from body that differs from remote by enabling preserve=true, just like there is a remote_unsecured_without_perms, this could be remote_with_perms...

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by François ARMAND over 8 years ago

Assignee set to Benoît PECCATTE

Benoit, could you take a look to that?

Actions

Copy link

Updated by François ARMAND over 8 years ago

Thinking a little more about that, isn't there a risk to let the attacker gain a huge information by letting he knows what exactly is encrypted on a communication (i.e a kind of known plain text attack ?). Not sure it is even remotly relevant, and what is more likelly (seems that your concern is more likelly than mine), just wanted to track it here.

Actions

Copy link

Updated by Benoît PECCATTE over 8 years ago

Why not but this could have an impact on low end nodes likes raspberry pi.
The better solution would be to make this an option.

Making it an option in system technique is possible.
Making it an option in initial promises must wait a later release when both are merged.

Actions

Copy link

Updated by Janos Mattyasovszky over 8 years ago

The tools do not change IMHO that often that it would make a huge difference... And it was just changed to unencrypted to solve a completely unrelated issue.

Actions

Copy link