How can I get AES encryption working?

Hi, I want to get a dedicated Xonotic server running on Linux, and was curious on how to get AES working.

I'm currently on Fedora 23 Server with Xonotic 0.8.1 (the official zip). As-is, the in-game server browser claims my server is missing the auth library.

From what I understand, I need rijndael. Fedora seems to have the libaesgm package which by-description says "Library implementation of AES (Rijndael) cryptographic methods", which seems to be the thing Xonotic would need for this.

According to random info online, I would need the libd0_rijndael.so.0 library, but if the package above is the same thing; Fedora has it packaged as libaesgm.so.0, has it installed by-default (on both Workstation and Server, so if the client needed access to it, it's there), and has it sitting in /usr/lib64. I tried symlinking it with sudo ln -s /usr/lib64/libaesgm.so.0 /usr/lib64/libd0_rijndael.so.0 to no avail.

I start the server with xonotic-linux-dedicated.sh, which in-turn uses the xonotic-linux64-dedicated executable, so it doesn't appear to be an architecture mismatch.

The only other idea I have is that Xonotic from the zip isn't compiled with rijndael/AES support, which I gather would mean I'd have to compile Xonotic to have the support. I'm not entirely certain where to exactly begin with compiling it though (the main Gitlabs page has a few projects listed that look like they'd be important; mainly the pkgs, darkplaces, xonotic itself, and d0_blind_id), and I didn't seem to see any quick-reference Linux compile guide anywhere. I was expecting something along the lines of downloading any needed dependencies, pull the git source in, compile it with GCC, install it, and be good to go.

The only other idea I have is that Xonotic from the zip isn't compiled with rijndael/AES support, which I gather would mean I'd have to compile Xonotic to have the support. I'm not entirely certain where to exactly begin with compiling it though (the main Gitlabs page has a few projects listed that look like they'd be important; mainly the pkgs, darkplaces, xonotic itself, and d0_blind_id), and I didn't seem to see any quick-reference Linux compile guide anywhere. I was expecting something along the lines of downloading any needed dependencies, pull the git source in, compile it with GCC, install it, and be good to go.

There's some legal requirement for AES not to be pre-compiled. Did you check out
https://gitlab.com/xonotic/xonotic/wikis...ory_Access
about how to compile?

Also, don't forget to compile for the server with:

Code:

$ ./all compile dedicated

in addition to the clients:

Code:

$ ./all compile sdl (or any other options, such as glx)

To run your server, do

Code:

$ ./all run dedicated -sessionid myServer1

To run your client, do

Code:

$ ./all run sdl -sessionid myClient1

Feel free to post error messages if you have problem compiling.

Thanks for the info; I followed the instructions and got Xonotic's source and used their all script to compile and run the server, but I still don't seem to have AES support (my server in the server browser still claims the auth library is missing).

What's the exact error message?

What's the exact error message?

When browsing the info on my server from the in-game server browser:

Encryption: N/A (auth library missing)
ID: N/A
Key: N/A

This is the entire build log: http://pastebin.com/5Use9wnN
And here is the server start log: http://pastebin.com/Si46msGG

I don't necessarily see anything wrong in either log though aside from not being able to generate a key (from my understanding, a key can only be generated once a week, and I made the mistake of deleting my key early on)

I saw the crypto library compiled so it should be working. Could you regenerate the keys? (backup if you need to)

Code:

$ rm -f ~/.xonotic/key_*

$ ./all run dedicated

I saw the crypto library compiled so it should be working. Could you regenerate the keys? (backup if you need to)

Code:

$ rm -f ~/.xonotic/key_*

$ ./all run dedicated

I think I still need to wait the timeout for generating keys; after running the rm command above, I still have Error response from keygen server: Not allowed

Do I need the keys to be signed in order to use AES? If so, is there any other way to sign the keys aside from waiting?

Edit: Changed my IP and got the key generated, but still don't have AES support :/

At this point, this is beyond my understanding. Can some senior dev chip in?

I figured it out and I feel pretty noob for not figuring it out earlier; but since the server needs AES compiled to offer it... it makes sense the client would also need the support compiled in too :p I just assumed the server only needed the support and thus, only compiled the server from git before, and used the default xonotic client that comes in Fedora's repo to connect.

Compiling a git build client gave me the ability to see AES-supported servers, and shows that my server also supports AES.

Was sort of hoping to just have all users have the ability to use AES, but I don't think it's too realistic to expect everyone to grab the source and compile for it. But I guess it'll be good just to have it around regardless.

I'm glad it's resolved. Could you add [solved] in the post title?