Quote: |
I think there should be an option to change screen resolution. |
ExplodyThingy wrote: |
1. IT can display an invincible ship at the center of the map, but so can bots. Can people actually view the ship local? So far from that list I can see things that bots can do, but no one views the games via bots.
2. Why does a client have a user database? 3. Are you ever going to release this, the prealphas, or teh sources? |
Qndre wrote: |
The "user database" stores the names for the userIDs and the userIDs for the names, so if I get a message packet at example, I can look into the database, which name the user with userID "..." has and display his name.
|
Quote: |
The "settings database" stores settings in "cells" so you can lookup what the initial energy is (for example). |
Quote: |
The "central database" stores things which are used in multiple modules, like NRG, etc. |
Quote: |
Every plugin (there is a plugin interface) can access the database via read/write access if user wants to. With plugins you can modify the behaviour of the client (change everything in the database, send chat messages, send packets, look which packets the client recieved). |
Quote: |
I'm going to release the client open-source if it's useful for something and if there aren't plenty of bugs in it any more. I'll release it BEFORE I implement the CONT encryption because I don't think I can do it. So you'll get a VIE client in the end (maybe for use by zone MODS, etc.)! |
ExplodyThingy wrote: |
And youre writing this data to disk instead of storing it in memory why? How completely hackable. So its an array instead of a struct WHy not just have pointers to the aforementioned memory? Again, what I jsut said. Like merv if that helps you. |
Nintendo64 wrote: |
Only suggestion for now, SETTINGS SHOULD NOT BE WRITTEN TO A FILE OR SHOWN TO THE USER OR PLUGIN DEVELOPER AT ALL, that alone can get your client not supported everywhere, nobody likes the idea of someone getting access to their settings besides the sysop. |
Qndre wrote: |
Just tried out some assembly. I wrote a program to read data out of the stack in hope to get the call "subgame2" does to get keystream from CONT but there doesn't seem to be any security hole like that! ![]() _ Also wrote some MacID and PermID spoofing code but it doesn't work. Neither for CONT nor vor VIE Subspace. _ This software can be downloaded as Source-Code, Objectcode or Binary distribution on my download-centre:http://www.subspace-addicted.de.vu/downloads/ _ PS: I haven't stolen the code from anywhere - I've written it on my own. |
packets3.txt wrote: |
C2S 0000 34 97 97 5C AF B3 69 AB
C2S 0000 74 D7 D0 91 12 37 6F B3 C2S 0000 14 B7 70 7A F4 8D FE 9A C2S 0000 54 F7 FC 3A 10 FF 99 78 |
Mr Ekted wrote: |
You should post it here so we can see how secure it is. |
Mr Ekted wrote: |
Do you understand that if the algorithm is known, then it is useless in a client to prevent client-side tampering? Publishing your algorithm destroys it. |
Quote: |
You seem to be intent on hacking into Cont and causing trouble. I don't really understand your motives. |
Quote: |
Do you understand that if the algorithm is known, then it is useless in a client to prevent client-side tampering? Publishing your algorithm destroys it. |
SSCU 17th Parallel, SSCU Trench Wars and SSCX Extreme Games wrote: |
You do not have permission to play in the selected zone... blah blah blah ...meanwhile please choose another zone. |
-Smong- wrote: |
If you think the staff are unreasonable you can either tolerate it or go somewhere else. |
-Smong- wrote: |
There is a black list .txt similar to permit.txt, if you stick someone's name in it they can't enter the zone. I guess this is what staff might have done to keep you out, and let everyone else in. I remember someone said they couldn't get into TW with the name 'analyser' because it contains 'anal'. |
Mr Ekted wrote: |
Um. So you wrote a bunch of ASM that doesn't work. |
Cyan~Fire wrote: |
I know of no popular zone that has switched to permission-only. It would only hurt themselves anyway. I think just you are being targeted, Qndre. |
Mr Ekted wrote: |
Maybe some day, he'll magically remember he can't program, and go back to working the drive-thru. |
Qndre wrote: |
If you run "continuum.exe" with the command line parameter "S" it writes you a "scrty" and a "scrty1"-key to disk. |
Qndre wrote: |
That's my key to Continuum encryption. I'm already having some exact information about how the encryption algorithm works but I don't think it can be written in BASIC, so I'll need ASM - so - forget it. |
Qndre wrote: |
My client will turn out as a fucking VIE client that no one wants to use - even not Mods because they could just use Subspace if the wanted to have a VIE client. |
Cyan~Fire wrote: |
Darnit! We all had no clue this would happen, as shown by us telling you it would all along! |
Cyan~Fire wrote: |
Not bad, but you could still get them from a server folder anyday. |
Qndre wrote: |
[..]
True but should I copy the whole subserver into my client? ![]() |
Dustpuppy wrote: |
So you're just going to copy continuum.exe and run it with S instead? |
Dustpuppy wrote: |
You also said your client was open sourced, perhaps we could have a look? |
Qndre wrote: |
Found something out: If you run "continuum.exe" with the command line parameter "S" it writes you a "scrty" and a "scrty1"-key to disk. That's my key to Continuum encryption. I'm already having some exact information about how the encryption algorithm works but I don't think it can be written in BASIC, so I'll need ASM - so - forget it. My client will turn out as a fucking VIE client that no one wants to use - even not Mods because they could just use Subspace if the wanted to have a VIE client. ![]() |
Qndre wrote: |
[..]secure but open-sourced |
Mr Ekted wrote: |
No such thing (in this context). |
Mr Ekted wrote: |
Getting scrty and scrty1 files is pointless. They are unique for every zone. |
Quote: |
Feel free to hack your own server all you like. |
Qndre wrote: |
How can things like SSL be open-sourced AND simultanously secure? |
Mr Ekted wrote: |
Because in most online situations, the only important thing is that no one who is watching the traffic can decrypt the data. You are protecting the packets from view by a 3rd person. In Continuum, the packets must be protected from view/modification by the person running the client. It is a completely different security issue than most online applications where SSL, VPN, RSA, etc are used. |