← Forum archive

hi

An archived conversation. New replies are closed.

iced
there are actually no words to properly respond to that. if you left holes, they're there, you just don't know about them. i'll find them.

also why aren't you utilizing a gateway service or vpn? you have rdp public facing. you don't have holes you have a block of swiss cheese.
Folder
I assume you're here to help fix security issues, or at least point them out, so thanks!

And yea swiss is gross.
Kawasaki
So far he has been very helpful in pointing out a few things I have missed so its very much appreciated.
NiteHawk
It's fine, Ry likes breakin shit and finding exploits. He did it in Kaos all the time and would let us know.. I don't mind him fuckin' around, hes good at it. 8)

Solved a couple things so far anyways. All good.
NiteHawk
The only reason I added that was to prevent clients from being created, not so much to protect the data being sent.

But I should probably be using something more proper rather then a basic terminal to connect, SSH or whatever for that sort of stuff. Anything left in the client is unfortunately easy to find if you know what you're lookin' for.
iced
ssh would be a nightmare to implement. you'd be better off using sslstream in the long-run. it'd make doing anything a lot more difficult than relying on encoding base64 and encrypting to 128bit. and it's easy to implement.
NiteHawk
ssh would be a nightmare to implement. you'd be better off using sslstream in the long-run. it'd make doing anything a lot more difficult than relying on encoding base64 and encrypting to 128bit. and it's easy to implement.


Yeh I'll look into it. Networking hasn't been my forte. I don't think you can really ever be 100% secure but suppose can be a pain in the ass in doing so. I was actually intending on changing it though with the new client anyways (or was going to look into it). Someone else (Meglio) pointed out the same issue you're talking about though in the networking portion.