hi
Re: hi
So far he has been very helpful in pointing out a few things I have missed so its very much appreciated.
Re: hi
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.
Re: hi
iced wrote: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.
Re: hi
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?
Who is online
Users browsing this forum: No registered users and 168 guests