Encrypt traffic between firefly and database #2
Labels
No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/firefly-iii#2
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As can be seen here:
coop-cloud/organising#114
Unless you have worries that your in-stack containers can be addressed publicly, then this is probably overkill? We're not doing this with any other apps fwiw. Open to reasoning to change that but that's where we're at now.
My understanding of docker networking is extremely basic but from what I understand you can sniff trafic on internal networks by performing some kind of ARP spoofing. While it's a highly improbable scenario, preventing it shouldn't be too difficult.
Here's a 52 page pdf about attacking containers that I skimmed over, saw C snippets and immediately closed: https://www.nccgroup.com/globalassets/our-research/us/whitepapers/2016/june/abusing-privileged-and-unprivileged-linux-containers.pdf
Also I think it's better to talk about it in here
coop-cloud/organising#114