The naked truth of #cybersecurity
-
The naked truth of #cybersecurity
-
Leo Bistmansreplied to BeyondMachines :verified: last edited by
@beyondmachines1 only 30 years ago the concept of firewalls was introduced.
The saying back then it was a temporally complexity needed until the software would be fixed.
-
@LeoBistmans @beyondmachines1
That was a good one.Considering that, we know from theoretical computer science that we cannot even prove whether an algorithm will terminate or not.
So how exactly are we supposed to make sure that software is โbullet-proofโ against attacks? Especially as what was benign yesterday can be considered an attack tomorrow.
-
Natasha Nox ๐บ๐ฆ๐ต๐ธreplied to Andreas K last edited by
@yacc143 @LeoBistmans @beyondmachines1 Would @librecast change anything about this? I know about Multicasts potential impact on server infrastructure and network design, but not security. I'm a bloody amateur in this field but still curious.
Wouldn't all ports be closed and the IPs mostly unknown using it? @dentangle -
Brett Sheffield (he/him)replied to Natasha Nox ๐บ๐ฆ๐ต๐ธ last edited by
@Natanox @yacc143 @LeoBistmans @beyondmachines1 @librecast As usual, it depends. For something like software updates or other static content a multicast server can sit behind a completely closed inbound firewall with no listening ports and never accept any direct communication from clients. If the local router tells it there are members of a group, it sends, if not, it stops.
So, yes, in some cases there are security advantages, but it's a complex question to answer.