nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to secure a opendeploy receiver?

RonaldV

Hi,

does anybody know how 'secure' a opendeploy receiver really is?
how does a receiver know for sure that the sender is actually the sender?

What about:
- ip spoofing
- man-in-the-middle
- buffer overflows
- propriety protocol vulnerabilities
- other ordinary attacks

Does encryption help to prevent these types of attacks?
What is a generally accepted good-practice on this issue?
How do you secure your od-receiver?

Hope to hear from you

Find more posts tagged with

Comments

nipper

I have been asked that before but it has not been an issue. Since port 20014 is open from the corp network and the www server is in a DMZ (only port 80 is open to the side going to the internet), any attacks, spoofing, etc would have to come from inside your organization.

Also OD uses its own handshake, so someone would have to know what that protocal is to spoof.

RonaldV

Thanks Nipper for your answer.

To me it sounds like that is not security but obscurity. :-) Anybody on the inside with a network-sniffer might be able to decode the handshaking.

Anybody else on this?

ISCBorisB

Thanks Nipper for your answer.

To me it sounds like that is not security but obscurity. :-) Anybody on the inside with a network-sniffer might be able to decode the handshaking.

Anybody else on this?

If you already have an "insider with the sniffer", are you so sure that OD is your biggest problem?