X-Demo

Sweet, thanks Jowie! So glad I didn't have compile wine this time around, the compilation process for wine (for running win32 binaries) on 64-bit Linux looked particularly annoying . Anyways, works for me on Mint 17.

Numpf took a quick look at the pull request! https://bitbucket.org/grelminar/asss/pull-request/1/chatnet-websocket-ssl-support/diff#comment-1335052

I've committed my changes here: https://bitbucket.org/X-Demo/asss. I'll be making the pull request to grelminar/asss shortly... P.S. Thx for hijacking my thread, pfft!

Hmm, I don't see why they "can't"... Players "can" use any username and password they want as long as it's not taken / the password matches (doesn't matter whether the server is connected to the SSC biller, their own biller or not connected to a biller at all). The whole point is that you can verify SSC login credentials without having to get access to the SSC biller directly. Ideally this whole OpenId thing should be done directly with SSC biller but I figured I'd add the few lines of code it required as I've heard it's very hard to get access to the SSC biller. Since Subspace.co isn't verifying SSC credentials, how would you know I'm the real X-Demo and didn't just type "X-Demo" into the name field when registering? It also would've been irritating if someone already registered using "X-Demo" here before I did.

What you mean get SSC logins to work without SSC billing exactly? And what would be the point if nothing was actually connected to SSC? Essentially indy ASSS servers could use SSC credentials... But now that I think about it, it's a major security issue just waiting to happen. For example, can indy ASSS zones be trusted not to steal your SSC password?

Hard to forget KcB and you all, that may have been the highlight of my SS career too. And yeah, I was on Verby too . And Long Patrol, before that Redwall Guardians(?) - those were in Turf Arizona right? I think my alias at the time was Sir Jesse. Ah the good ole days.

When I realized that making an OpenId provider was possible and that high-availability was a necessity, I started thinking that doing it this way is not exactly ideal. In my mind, ideally, the OpenId service should be working with the authoritative source of the auth data - the biller itself. I'd much rather find a way to work with the SSC biller directly - though I've been lead to believe getting access to this is extremely hard to get lately. Truely unfortunate given availability of so many public authentication systems like OpenId. With SS OpenId it may even be possible to at least allow SSC logins to work with a modified ASSS server without SSC billing... Although, many things wouldn't work right, like ?usage, scores?, chats, squads, etc.

@Dr Brain: I was hoping to get ASSS repo access on Bitbucket to a feature branch so it could be looked over and played with easily. Also I had a bunch of MinGW build fixes I had hoped to get off my hands that might clutter up my patch, lol. Maybe I'll just clone the repo and get my branches that way . Speaking of fixes, not only do I want to fix up all the warnings I can when building (MinGW is almost a hopeless case due to the windows compat hacks), it might also be fun to try compiling ASSS with clang as that might generate even more warnings. @Jowie: I integrated it myself, though since I began developing using Windows I found that MinGW's OpenSSL just repeatedly crashed. When I switched OpenSSL's official? Windows installer (http://slproweb.com/products/Win32OpenSSL.html) it worked like a charm. Furthermore, I found a way to share the same TCP port ChatNet is using to support both plain and SSL encrypted connections on the same port! @Cheese: Certainly a possibility, I've been looking into Discretion a lot lately but since it plain just crashed when I first ran it I'm not sure how far along it got . I've also been looking into Python-OGRE and other mixes of higher(ish) level gaming SDKs. With the idea of not reinventing the wheel and speeding up development using higher-level languages. Though that approach kinda conflicts with really wanting an authoritative server (like Counter Strike has, etc) for security/lag mitigating purposes.

So I realized I don't use Pidgin much anymore. Lately I've been working on an update to ASSS's ChatNet module. Perhaps after those projects are completed I'll take another look at the Pidgin plugin.

I didn't like the idea that ASSS's ChatNet protocol is raw text (including passwords). So I've been working on updating ASSS's ChatNet module. The features I'm working on are: SSL encryption [DONE]WebSocket support [DONE]Required Biller Login (ie. logins will be denied if the billing connection has been lost) [DONE]1 shot HTTP credential verification [SKIPPED]Rigorous testing of the new features/code [COULD ALWAYS USE MORE ] When I finish, I'm hoping ASSS will accept my changes otherwise I can provide the module in binary/source form. With WebSocket w/ TLS encryption (WSS) I'm hoping to create an HTML5 SS web-chat site that connects directly to an ASSS-enabled zone w/ the updated ChatNet module. With the 1 shot HTTP credential verification (and required biller login), I'm hoping to create an OpenId service that will allow both the web-chat and other websites to enable logins using your Subspace/Continuum login credentials, like how you can log in to/register with certain websites with your Facebook/Twitter/LinkedIn/Google credentials. Although without multiple ASSS servers running the new code, this won't be reliable; a problem since failover capabilities/high-availability is pretty much a necessity for services other sites depend on. --Updates-- 9/23/2013: -Fixed the "crash bug" (was a debug assertion that lead me to the actual bug) -Forked ASSS on Bitbucket (still hoping to get the changes pulled back) 9/30/2013: -Can't test the Windows build with Continuum due to ancient security.dll files and API breakages due to poor design (the design could be on purpose to make reverse engineering harder even though that's been done already apparently). -I'm debating reversing the ASSS security library anyways so I can release updated "security.dll/so" binaries that won't break as easily (static compiled [glibc version independent] if possible and unchanging APIs), as well as some for other platforms and architectures if requested. (Currently I want one for Armv5te.) (Also, I'll have to make sure those binaries are at least as hard to reverse as the current ones.) -I plan to commit the current code to a branch in my forked repository although it needs quite a bit of work before I'll deem it ready for a pull request. (re-organization, cleanups, testing, valgrinding, porting to Linux, adding configuration directives for global.conf, README updates for how to generate SSL certs, etc) 11/02/2013: -My computer died, though not my hdd thankfully. I took the opportunity to switch to Linux and now have my dev environment ready to go now. -While reverse engineering the security library I found out a few reasons why it's not more abstracted from the rest of the code. I probably won't be spending more time on reversing it as I don't see the point. 11/09/2013: -I've committed my changes here: https://bitbucket.org/X-Demo/asss. -I'll be making the pull request to grelminar/asss shortly...

That'd certainly make everything a *lot* simpler =P. The only hiccup I see is that pinkSTAR want's div's OK on this before proceeding. But I have a map and the settings all ready now .

Interesting . I agree, no doubt there'll be tons of things I can learn from your script. Thanks for the heads up on a few of the gotchas as well .

Hi all, I've started writing a Pidgin plugin that can connect to ASSS/ChatNet intended to be used with an SSC ASSS zone like Hyperspace so you can chat to TW, etc. My main motivation from writing this plugin is to help me become a little more available/active in my TW league squad and hopefully for aswz if it can be revived . I'm hoping it'll be useful to other people too, should I complete it. So far the code is a complete mess as I've started with the IRC plugin and rewrote/ripped out functionality I didn't need as I go along due to the poor documentation for writing pidgin plugins. After about 2 days of coding, it can connect and send/receive priv messages, but that's about it for now . Should I find the motivation, I'll see about adding: -buddy presence (querying via ?find) -chat support -squad chat support -?message support If/When the plugin becomes more useful and the code less messy I'll upload the source and Windows and Linux binaries to GitHub or something . - X-Demo

Hey all, Cintra and I have been talking to some of the powers that be in TW. Seems we can probably get an aswz sub-arena in TW once we have the maps and settings. (Just came across: http://maps.aswz.org, might be all we need if those can be adapted for subgame.) Some Benefits: -TW seems to be a more active zone than Chaos -Could probably entice players to try it out through bot announcements to pub -Hosted games (maybe with rewards of TW's pub currency) might also entice players Also, I've been thinking about joining staff (mod and/or bot developer) for TW. I wouldn't mind taking a stab at rewriting the old pub bot for TW's bot core . Thoughts? - X-Demo