Qndre wrote: |
before I start to implement them |
Mine GO BOOM wrote: |
Keep your time spent on making your client working well before you attempt to spend a great deal of time on encryption. |
CypherJF wrote: |
Won't do much good, because they change on each execution don't they? |
Mine GO BOOM wrote: |
Its not like those keys are just XOR with the data like VIEs. |
Mine GO BOOM wrote: |
Umm.. having a table of keys, in a format that is unknown to you (why should it be unknown?), won't help you much. |
Mr Ekted wrote: |
provided you knew (provided I knew? I do) how to use the files to encrypt packets, and you supported the additional Cont protocols |
Qndre wrote: |
Sorry but that's not right. If you delete them and only run the server (and don't connect with a client) then they are also generated. Just delete them and run "subgame2" without connecting to it and they will be generated. |
Qndre wrote: |
No they don't. Load the "scrty" into notepad, run subgame2 and load it again. You'll see it has been changed by subgame2. Then try the same with "scrty1". Load it into notepad, run subgame2 and open it again. And you'll see it has NOT changed. |
Mine GO BOOM wrote: |
Incorrect. Continuum itself makes those files, just subgame2 tells it to dump them to a file. Try this with just the VIE client and you'll notice. |
Cyan~Fire wrote: |
Have you ever thought that maybe the server creates just an incomplete 'scrty1' file when you first run it and then fills it out when a client connects? |
Mr Ekted wrote: |
They are generated by the Continuum client. |
Mr Ekted wrote: |
Qndre asks for help, we answer him, and he proceeds to tell us all we are full of shit. |
Qndre wrote: |
But what if you don't have a Continuum client installed on your system but only the server? Then "subgame2" won't be able to run or won't be able to use encryption? Doesn't seem very plausible to me. |
Smong wrote: |
subgame uses version1/subspace.exe. The latest continuum client is renamed to subspace.exe and put in that folder. |
Mine GO BOOM wrote: |
[..]
Its the same way the server works. It looks inside a subfolder for the Continuum client's exe. If it finds it, it loads it up and gets access to the encryption. If it cannot find it, it doesn't get access to the encryption. [..] |
Smong wrote: |
Why do I get the feeling no one reads my posts? Have a look about 5 posts up, 24th March 2004, 11:01 pm.
|
Mr Ekted wrote: |
They are. They are generated by the Continuum client. |
Qndre wrote: |
Sorry but that's not right. If you delete them and only run the server (and don't connect with a client) then they are also generated. Just delete them and run "subgame2" without connecting to it and they will be generated. |
Mr Ekted wrote: |
Here we go again. Qndre asks for help, we answer him, and he proceeds to tell us all we are full of shit. I am tired of his attitude, and will no longer help him. Good luck with your "one packet per month" project. Bye. |
nintendo64 wrote: |
[..] even thought you might think something works some specific way, you could be the one wrong. That's sometimes annoying along with some people you explain to them how it works [..] The question i have on my mind is... Subgame knows exactly the location of the encryption area in the Continuum Client. I thought there was some kind of "secure-space" interface used in CTM Client to grant access to others applications such as Ekted DLL. If Subgame has that kind of access wouldn't that be foolish? (considering how easy you can retrieve data from Subgame or Fix.dll for that matter) |
Qndre wrote: |
"scrty" and "scrty1" are arrays |
Qndre wrote: |
There is also a file in ASSS server called "security.so". Maybe it's also related to encryption. If my information is right, "*.so" files are just sourcecode files encrypted with a quite old technique called "secure-sourcecode". |
Quote: |
Or, you could just look it up. Scroll down a bit till you get to the UNIX Shared Library Function section and read that. |
I wrote: |
ASSS has "security.*", which contains all the encryption information. |
Mr Ekted wrote: |
Typical Qndre dialog...
Qndre: MD5 is the easiest encryption ever. Took me 2 minutes to break it. Other: MD5 is not encryption. Qndre: Yes it is. It hides information. Other: Encryption is reversible. MD5 is one way hash. Qndre: I never said MD5 was encryption. I just said it was very tough. |
nintendo64 wrote: |
what ekted means about your "attitude" Qndre is that if you don't know how something works, and you ask someone how it works, then why do you tell them, they are wrong? even thought you might think something works some specific way, you could be the one wrong. That's sometimes annoying along with some people you explain to them how it works and then they end up trying to explain to you how it works (Even Thought THEY DON'T KNOW). |