Notifio's single licence check doubles as its only authentication, and the copies have stayed consistent
Notifio has no user accounts, passwords, or sessions, so every privileged request relies on a licence email and activation token pair. The author found that this licence check is the sole authentication mechanism and that it is implemented in several places. A shared helper returns null for any mismatch, so responses cannot reveal whether a token exists or belongs to someone else. The notification route duplicates the same query and conditions rather than calling the helper, and it returns a 403 where the validate route returns a 200 with valid set to false. The author notes that the duplicated logic currently matches but has no mechanism to detect future drift.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in