Tree: 8c551de2ab

cached-config-operations

main

revert-7033-patch-1

test_dylint

threat_model

v2-registration

0.10.0

0.11.0

0.12.0

0.13.0

0.9.0

1.0.0

1.1.0

1.10.0

1.11.0

1.12.0

1.13.0

1.13.1

1.14

1.14.1

1.14.2

1.15.0

1.15.1

1.16.0

1.16.1

1.16.2

1.16.3

1.17.0

1.18.0

1.19.0

1.2.0

1.20.0

1.21.0

1.22.0

1.22.1

1.22.2

1.23.0

1.23.1

1.24.0

1.25.0

1.25.1

1.25.2

1.26.0

1.27.0

1.28.0

1.28.1

1.29.0

1.29.1

1.29.2

1.3.0

1.30.0

1.30.1

1.30.2

1.30.3

1.30.4

1.30.5

1.31.0

1.32.0

1.32.1

1.32.2

1.32.3

1.32.4

1.32.5

1.32.6

1.32.7

1.33.0

1.33.1

1.33.2

1.34.0

1.34.1

1.34.2

1.34.3

1.35.0

1.35.1

1.35.2

1.35.3

1.35.4

1.35.5

1.35.6

1.35.7

1.35.8

1.36.0

1.37.0

1.37.1

1.37.2

1.37.3

1.37.4

1.37.5

1.4.0

1.5.0

1.6.0

1.6.1

1.7.0

1.8.0

1.9.0

1.9.1

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '8c551de2ab'

${ noResults }

Commit Graph

7 Commits (8c551de2abc4937d5c21d6ac1a5dfe99154f7032)

Author	SHA1	Message	Date
ICantThinkOfAName-tech	8c551de2ab	Use the email token settings for Send verification codes Reuse `EMAIL_EXPIRATION_TIME` and `EMAIL_ATTEMPTS_LIMIT`, like the email 2FA codes, instead of hardcoded values. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	4 weeks ago
ICantThinkOfAName-tech	19e855d35f	Send the Send verification email in the background Sending the code only for allowed emails made those responses take as long as the SMTP round trip, which tells allowed and unknown emails apart. Mail the code in the background so both answer the same way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	4 weeks ago
ICantThinkOfAName-tech	024e3a6689	Add Item Sends (temporary vault item sharing) Support the Item Send type used by the Bitwarden clients (2026.10+) to share a single vault item through a temporary link. - New `Item` Send type; the item is encrypted client side into one opaque blob, stored with its item id in clear - Item Sends require email verification - Only items the user owns, or organization items they can edit and see the password of, can be shared; deleted, archived and SSH key items can't. Access is checked on creation and when the item changes - Accesses are counted like Text Sends, so one-time links work - Opt-in through the `pm-34203-temporary-item-sharing` client feature flag; while disabled, Item Sends can't be created and existing ones are hidden from owners and recipients Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	4 weeks ago
ICantThinkOfAName-tech	c46c22139b	Add email verification for Sends Allow Sends to be restricted to a list of email addresses. Recipients request a one-time code by email through the `send_access` grant and exchange it for an access token, matching the upstream flow. - Store `auth_type` and `emails` on sends, with an additive migration - One-time codes: single use, constant-time compared, invalidated after 5 wrong attempts, 60s resend cooldown, 5 minute validity - Unlisted emails get the same response as listed ones and no email is sent, so recipients can't be enumerated - Access is gated on the stored auth type and fails closed when a Send doesn't hold the emails or password its auth type requires - Shared create/update handling of authType; it is inferred when missing, like upstream, for clients that don't send it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	4 weeks ago
Daniel García	f4f1a8e105	Send API cleanup: remove legacy endpoints and align access with upstream (#7806)	1 month ago
Daniel García	46ae59eaf4	Trusted proxy support, unauthenticated rate limit & other fixes (#7472) * Trusted proxies, unauthenticated rate limits and various fixes * Fix get_groups_data * Fix get_groups_data when not using full_access * Fmt * Fix org import * deduplicate send validation	4 months ago
Timshel	5c5e8e1a6f	2026.6.0 send support (#7346) * 2026.6.0 send support * Prevent creating and editing a Send with email verification * Review fixes --------- Co-authored-by: Timshel <timshel@users.noreply.github.com>	4 months ago