Anonymous | Login | Signup for a new account | 22.12.2024 02:17 CET |
Main | My View | View Issues | Roadmap | Wiki |
View Issue Details [ Jump to Notes ] [ Wiki ] | [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0000032 | Obsidian Conflict | (No Category) | public | 22.08.2010 19:56 | 26.09.2010 17:39 | ||||||||
Reporter | mmavipc | ||||||||||||
Assigned To | |||||||||||||
Priority | low | Severity | feature | Reproducibility | N/A | ||||||||
Status | acknowledged | Resolution | open | ||||||||||
Projection | none | ETA | none | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | 0.1.3.5 | Product Build | |||||||||||
Target Version | SVN | Fixed in Version | |||||||||||
Summary | 0000032: Dynamic SteamID checks for donators/mod-banned people | ||||||||||||
Description | They should be made dynamic, but encrypted with a public-key system. In a public-key system, things encrypted with the private key can only be decrypted with the public key, and vice-versa. Things encrypted with the public key can't be decrypted with the public key. If you kept the private key on your end, and give the public key to the clients(server.dll and client.dll). If this is used in-combination with the current static system, I think it could be a great addition. | ||||||||||||
Tags | No tags attached. | ||||||||||||
Attached Files | |||||||||||||
Notes | |
(0000026) neico (administrator) 22.08.2010 21:11 |
isn't really worth the work as it's going to be replaced anyways |
Copyright © 2000 - 2024 MantisBT Team
Time: 0.0519 seconds. memory usage: 8,319 KB |