Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I will say that a youtuber said in order to get your server to show up in the in-game menu, he advised posting your server to arkservers.net and that was TERRIBLE advice.
My VNC got hit with a brute force attack and I can no longer use it outside the LAN because every time I try to start it up, I get hit with non stop connection attempts, so I had to remove the port forwarding.
I brought it up on the UltraVNC board and the admin said to just change my port for VNC, but one of my oldest friends who is lead programmer for a shipping company told me hackers could just do a port scan anyways.
I trust him more than the guy trying to get me to use his software.
Also, if this is your first server, I recommend you whitelist instead of using a password, unless you intend it to be public.
So we added a password too and the problem went away.
Changing the default port just makes it less likely that random bots doing a cursory scan of default ports will take a stab at you. But a determined adversary will do a full port scan.
VNC does not have the authentication back end to naively support proper defence against brute force attacks or modern authentication standards such as OAUTH/SAML. You're also exposing and increasing your attack surface area to yet another application when you should be minimising it.
VNC traffic in transmission that is encrypted will not protect you from a brute force attack as mentioned in the comment I was responding to. And neither will the traffic being encrypted protect you from software faults and CVE's relating to the software itself and unauthorised execution of arbitrary code on the endpoint itself.
By placing all unnecessarily exposed endpoints behind the VPN you are reducing the attack surface and protecting applications that are ill-designed for a determined adversary.
I have to secure this type of stuff in the enterprise all the time. Just because you personally do it all the time and you've not had any issues does NOT mean its a smart thing to be doing. Your perception of "secure" seems to be really narrow and missing a whole chunk of the picture.
I am not talking about encrypted transmission traffic or using a VPN to protect the data stream in transit.
But what I'm really referring to is avoiding exposing ports to internal applications on your network where possible.
Setting up a VPN server on your home router or PC allows you to remotely connect to it over the VPN without exposing vulnerable applications ports to the public internet.
By only exposing the ports required for the VPN allows you to protect multiple other internal applications that are not really designed to be accessed directly over the internet. Most VPN's also allow for more secure authentication than simple username+password.
But you keep at your survivor bias and arguing a completely different point.
Then when I completely debunked your statement as false information you decided to "double down" and make up all sorts of complete nonsense that has nothing to do with this thread, the conversation, VNC, or.. whatever it is that you're going on and on about to make yourself feel smart in public.
And now you're trying to attack me in public... 🤣🤣
I have no idea what your agenda is or what you think you're trying to do here but you certainly aren't succeeding at whatever it is. It looks like you're just trying to harass random people, hijack their threads, and start arguments for no actual reason.
I did NOT say that vnc was bad. I said that opening it up for across the internet was a bad idea and it is. Not that using it on the internet! The point is the ports open on the end points are what's vulnerable. Not the traffic in transit that you keep referencing. vPNing into the servers network before using VNC would protect against the brute force attack and port scanning the OPs comment mentioned.
That you can't discerned the difference between those things suggests that youre a lay person. Which is ok but maybe don't accuse people of having an agenda just because you don't completely understand what they're saying. This could have been discussed without the accusations.
Attacking you? I didn't attack you. You stated you opened the ports and were fine. Which is a survivor bias. Just because you've been fine doesn't mean it's a great idea. I've had to cleanup countless environments where such decisions were made and resulted in a data breach.
If you want to actually talk it out I'm happy to. But if all you're going to do is accuse me of having an agenda and spreading false Information then Ill leave you to it.
Take care