hi
An archived conversation. New replies are closed.
i'm here to break your game
hi ry
hi buddy
rgr. Didn't leave any holes to make admin accounts though, sry. Feel free to break shit.
What's really going to bake your noodle later on is, would you still have broken it if I hadn't said anything?
View linked image
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.
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.
Ew
i know right swiss cheese is not the best of cheese
8)
I assume you're here to help fix security issues, or at least point them out, so thanks!
And yea swiss is gross.
And yea swiss is gross.
So far he has been very helpful in pointing out a few things I have missed so its very much appreciated.
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.
Solved a couple things so far anyways. All good.
hellomarthawhatareyoudoinghereLUL762981balls
can i leave this right here
can i leave this right here
hellomarthawhatareyoudoinghereLUL762981balls
can i leave this right here
Go ahead. 8)
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.
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.
what about this one
9C852A5686A05AA60661BC8B2E67C5F16F403B03
9C852A5686A05AA60661BC8B2E67C5F16F403B03
what about this one
9C852A5686A05AA60661BC8B2E67C5F16F403B03
That's probably your unique ID
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.
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.
https://msdn.microsoft.com/en-us/library/system.net.security.sslstream(v=vs.110).aspx
if you're making a new client, it's a good time to learn something new then. you are using source control right?
if you're making a new client, it's a good time to learn something new then. you are using source control right?