mirror of
https://github.com/burrow-dev/burrow-server.git
synced 2026-11-18 17:27:50 -05:00
fix: device ids optional until players update to client 1.3.0
A sign-in without device ids is let in unless AJ_REQUIRE_DEVICE=1. An account seen on banned hardware is still refused, with the ban's reason, when its client sends no ids. The privacy policy no longer says the client cannot sign in without them.
This commit is contained in:
1 parent
31cbd87ff8
commit
13c2f04d52
3 files changed
+11
-7
No files matched your search
@@ -98,10 +98,12 @@ module.exports = {
|
||||
// cached in cacheDir. set AJ_OFFLINE=1 to serve from the cache only.
|
||||
upstreamContent: env.AJ_UPSTREAM || "https://ajcontent.akamaized.net/",
|
||||
offline: env.AJ_OFFLINE === "1",
|
||||
// the client's device ids (lib/devices.js): a sign-in without them (a
|
||||
// client from before 1.3.0, the official launcher, or one that left them
|
||||
// out) is refused. AJ_REQUIRE_DEVICE=0 lets them in, unknown.
|
||||
requireDevice: env.AJ_REQUIRE_DEVICE !== "0",
|
||||
// the client's device ids (lib/devices.js): with AJ_REQUIRE_DEVICE=1, a
|
||||
// sign-in without them (a client from before 1.3.0, the official
|
||||
// launcher, or one that left them out) is refused. off for now, while
|
||||
// players update to 1.3.0: they are let in, and an account seen on banned
|
||||
// hardware before is still kept out.
|
||||
requireDevice: env.AJ_REQUIRE_DEVICE === "1",
|
||||
deployVersion: env.AJ_DEPLOY_VERSION || "1830",
|
||||
// older builds the CDN still serves, asked in turn for a room file the
|
||||
// current build has dropped. 1828 is the last with the Summer Carnival.
|
||||
|
||||
+4
-2
@@ -439,8 +439,10 @@ const authenticate = async (req, res, from) => {
|
||||
send(res, 401, {error_code: 101, error: "address_banned", banned_seconds: world.moderation.PERMANENT, ban_reason: addressBan.reason});
|
||||
return;
|
||||
}
|
||||
// A banned computer (lib/devices.js): for good, whichever account.
|
||||
const deviceBan = device && devices.banOf(device);
|
||||
// A banned computer (lib/devices.js): for good, whichever account. a
|
||||
// client that sent no ids (before 1.3.0) is judged by the hardware the
|
||||
// account was seen on.
|
||||
const deviceBan = device ? devices.banOf(device) : devices.banOfAccount(account);
|
||||
if (deviceBan) {
|
||||
console.log(`[devices] "${account.username}" refused: hardware banned (ban ${deviceBan.id})`);
|
||||
send(res, 401, {error_code: 101, error: "device_banned", banned_seconds: world.moderation.PERMANENT, ban_reason: deviceBan.reason});
|
||||
|
||||
+1
-1
@@ -174,7 +174,7 @@
|
||||
<tr><td>What you choose to write or make: bio, Discord username (optional), Jam-A-Grams, wall posts, paintings, feedback</td><td>To show or deliver it as you asked</td></tr>
|
||||
<tr><td>Typed chat and whispers, with the room and time, and the words of Jam-A-Grams and wall posts, with who they went to</td><td>Moderation: reviewing reports and deciding on bans</td></tr>
|
||||
<tr><td>IP address at each sign-in, and sign-in times</td><td>Security: your sign-in history, limiting abuse, address bans, and finding accounts made to get around a ban</td></tr>
|
||||
<tr><td>Hardware hashes, sent by the Burrow client at each sign-in. The client reads a few identifiers of your device (its system id, hardware serial numbers, network card addresses, and a random id the client makes for itself) and turns each into a one-way hash before sending it; we hash them again with a secret key of our own. The identifiers themselves never leave your device, and the hashes cannot be turned back into them: they do not tell us who you are, what your device is, or anything else about it, and mean nothing outside this server. We also note if the identifiers look missing or altered</td><td>Only to prevent ban evasion: hardware bans, and finding accounts made to get around a ban. They are not used for tracking or advertising and are never shared. The client cannot sign in without them</td></tr>
|
||||
<tr><td>Hardware hashes, sent by the Burrow client at each sign-in. The client reads a few identifiers of your device (its system id, hardware serial numbers, network card addresses, and a random id the client makes for itself) and turns each into a one-way hash before sending it; we hash them again with a secret key of our own. The identifiers themselves never leave your device, and the hashes cannot be turned back into them: they do not tell us who you are, what your device is, or anything else about it, and mean nothing outside this server. We also note if the identifiers look missing or altered</td><td>Only to prevent ban evasion: hardware bans, and finding accounts made to get around a ban. They are not used for tracking or advertising and are never shared</td></tr>
|
||||
<tr><td>When you log in to the game, how long each visit lasts, and your total playtime</td><td>To show you your playtime, and for overall activity figures (how many people play and when) that staff use to run the server</td></tr>
|
||||
<tr><td>The number of players online, counted every minute</td><td>Overall activity figures. This count is not linked to anyone</td></tr>
|
||||
<tr><td>Reports, bans and their reasons, appeals, username rejections</td><td>Moderation and preventing ban evasion</td></tr>
|
||||
|
||||
Reference in new issue
Block a user