[DiscordArchive] Is there a specific function that ensures the parent reputations also receive 50% of the reputation
[DiscordArchive] Is there a specific function that ensures the parent reputations also receive 50% of the reputation
Original source
Is there a specific function that ensures the parent reputations also receive 50% of the reputation reward, or are they handled separately in the DB for rewards?
rektbyfaith
04-15-2022, 09:02 PM #1Archived author: Snowcraft • Posted: 2022-04-15T21:02:24.753000+00:00
Original source
Is there a specific function that ensures the parent reputations also receive 50% of the reputation reward, or are they handled separately in the DB for rewards?
Original source
i haven't messed with it too much so i'm not 100% sure the core reads it as written, but faction parenting and spillover are properties of `Faction.dbc`
rektbyfaith
04-16-2022, 09:01 AM #2Archived author: <o> • Posted: 2022-04-16T09:01:07.172000+00:00
Original source
i haven't messed with it too much so i'm not 100% sure the core reads it as written, but faction parenting and spillover are properties of `Faction.dbc`
Original source
you can reference this issue to find commits involved: <https://github.com/TrinityCore/TrinityCore/issues/25157>
As you can see, even if you're close to that tree it was a pretty messy migration involving multiple pulls, and the further from it your own tree is the more difficult it will be to migrate. The recommended way is always to update to the latest version.
It should be noted that while those pulls do improve security of the database itself in case of a leak (the salt was effectively useless since SHA1(username:password) was stored), they do not (and cannot) address the issue of passwords typically being sent in plaintext to servers during registration, allowing private server operators to very efficiently hack accounts on other servers by just recording the plaintext information that users give them, even though that is something that SRP6 _can_ address as a zero-knowledge protocol. The only solution to that problem is to implement the clientside SRP6 that wow uses in javascript and convince enough CMS systems to implement the protocol properly, improving the ability to detect and cast suspicion on servers that don't follow that transparency)
rektbyfaith
04-16-2022, 09:28 AM #3Archived author: <o> • Posted: 2022-04-16T09:28:02.012000+00:00
Original source
you can reference this issue to find commits involved: <https://github.com/TrinityCore/TrinityCore/issues/25157>
As you can see, even if you're close to that tree it was a pretty messy migration involving multiple pulls, and the further from it your own tree is the more difficult it will be to migrate. The recommended way is always to update to the latest version.
It should be noted that while those pulls do improve security of the database itself in case of a leak (the salt was effectively useless since SHA1(username:password) was stored), they do not (and cannot) address the issue of passwords typically being sent in plaintext to servers during registration, allowing private server operators to very efficiently hack accounts on other servers by just recording the plaintext information that users give them, even though that is something that SRP6 _can_ address as a zero-knowledge protocol. The only solution to that problem is to implement the clientside SRP6 that wow uses in javascript and convince enough CMS systems to implement the protocol properly, improving the ability to detect and cast suspicion on servers that don't follow that transparency)
1 Guest(s)
1 Guest(s)