* Initial commit for 2FA plugin
* Shut up netf
* Actually import this authenticator right into ASF, and add safeguards
* Further fixes
* Render device_id in the resulting maFile
- Make use of new UnixFileMode, always one native method we need to maintain less
- Add madness support for it, because new feature of course
- Add optional netstandard target and required compatibility for it, so I can test netf-oriented changes easier
We should increase our security by checking against revoked SSL certificates, just in case.
When using proxy, pre-authenticating makes sense since if user provided the credentials, we can be pretty sure they're required and save a roundtrip.
We have many clients and a single server, pushing additional work at the clients will typically degrade the effective speed with which the data can be transmitted, but will allow our server to handle more requests concurrently due to less bandwidth used, and will positively affect the bandwidth used for both server and the client.
This allows to blacklist even masters/owners, in result denying all trade offers from them while still honoring everything else, like commands.
Don't ask me why anybody would need it, ask @Ryzhehvost 😎
This is a severe edge case. We forgot to call base constructor during creating BotDatabase, which is funny because it wasn't the case for ASF database. This caused event listeners to not be recorded, and therefore changes not being saved. Normally this bug entirely slipped through because on first login, login key is normally saved into the database, and that part always generated the file, with or without the listeners. However, if somebody has UseLoginKeys: false, and doesn't set up ASF 2FA for the bot, and bot database doesn't exist, it won't get created on changes to other bot database properties, that is: farming blacklist, farming priority queue, match actively blacklist and trading blacklist.
Wow, this one is old, I don't know if we didn't have this bug since first version of ASF or something.
