ShareShield 4.0.1: security and reliability fixes
ShareShield 4.0.1 fixes what a full review of 4.0.0 found: stricter invitations, 8-digit recipient codes, safer reveals and billing, and API changes to check.
ShareShield 4.0.1 is out. It has no new features. It fixes what a full review of 4.0.0 found.
Security
- Invitations need a verified email. In 4.0.0, a member of an organisation could see its pending invitations and accept one by signing up with the invitee’s address. Now only someone who has verified that address can view or accept it. Member limits and assignable roles are checked again on acceptance, and pending invitations count towards the limit.
- Recipient codes are 8 digits, up from six. After 20 wrong attempts in total, codes for that address stop working and the recipient signs in instead.
- Sign-in. A password reset ends every existing session, verification links no longer sign you in, and ten wrong two-factor codes in 15 minutes lock that account’s second factor until the window ends.
- Removing a member from one organisation leaves their other organisations untouched.
- SSO setup no longer connects to private network addresses or follows redirects when it looks up your identity provider.
Fixes you might notice
- Opening a secret returns it before anything else is recorded, so a slow email or database write can’t lose it. If your browser gets no answer, the page now says it couldn’t confirm whether the secret was opened.
- Billing. Upgrading an organisation that already has a subscription opens the plan change in the Stripe billing portal instead of starting a second subscription. Once a paid plan is cancelled or expires, the free limits apply, and the billing page shows the limits that are actually enforced.
- Policy defaults. An organisation’s defaults now win over personal ones, and changing an unrelated setting, such as the theme, no longer saves defaults you didn’t choose.
- Auto-join domains now also cover verified password sign-ups and existing users signing in through the organisation’s SSO.
- Copy says “Copied” only when it worked, and the one-time API key and backup-code dialogs no longer close on Escape.
What you may need to do
- Re-send password secrets that have no passcode. 4.0.0 accepted API calls with
accessType: "PASSWORD"and no passcode, and opened those secrets for any password. They now refuse to open, and new ones get400. - Check how your integration reads status codes:
- An invalid, revoked or expired API key gets
401on v1 routes where sign-in is optional. It used to be treated as anonymous. - Burning or renaming a secret that isn’t yours returns
404(was403). - JSON bodies over 1 MB get
413. - Every
429carriesRetry-After. - v2 returns
400for malformed cursors and ids, and validation errors always includedetails.issues.
- An invalid, revoked or expired API key gets
- Recipient codes in the API are accepted at 6 to 8 digits, so codes sent before the upgrade work until they expire.
Send the next one as a link that expires.
ShareShield turns a password, key or file into a link that opens once and is then deleted. You can send a text secret without an account.
