Skip to content

Commit 4f25192

Browse files
committed
docs: note upcoming security fixes by the new acap lead
1 parent aa17e9f commit 4f25192

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

docs/pages/announcements/firebase-storage-2024.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,9 +137,11 @@ _All Firebase components service usage (including those not used by ACAP) will o
137137
Yes. <u>Some of the latest core deliverables</u> implemented for ACAP in its [2.0](/changelog/#version-2-acap-20) version [**introduced security flaws**](/changelog#acap-2-security-debts) not present in the initial ([1.0](/changelog/#version-1-acap-10)) version, which had strictly followed [security guidelines](/security) and adhered to best practices in web development security, effectively preventing these issues. Based on the following criteria, the new security flaws introduced in version 2.0 resulted in a **60% reduction in the established security from version 1.0**.
138138

139139
<Callout>
140-
> With ACAP 2.0+, a <u><b>new code maintainer and lead programmer</b></u> took over core development. You can check the [ACAP repository](https://github.com/amia-cis/acap-v2/issues/57) for more details.
140+
> With ACAP 2.0+, a <u><b>new code maintainer and lead programmer</b></u> took over core development and <u>made changes to improve development speed</u>. As part of this effort, they introduced a more flexible Firestore database setup, which streamlined workflows. But it also <u>loosened security rules</u>.
141141
>
142-
> To speed up development, they introduced a more flexible Firestore database setup. However, this also loosened security rules, raising concerns not present in version 1.0. The <u><b>same lead programmer</b></u> is aware of the trade-offs, and <u>since they made these changes, they’re the best person to contact for security updates and fixes.</u>
142+
> While these adjustments enhanced agility, they also <b>introduced security concerns</b> not present in version 1.0. This <u><b>lead programmer</b></u> is aware of these trade-offs, and <u>since they made these changes, they remain the best point of contact for security updates and fixes.</u>
143+
>
144+
> For more details on these changes, refer to this GitHub [issue](https://github.com/amia-cis/acap-v2/issues/57) in the parent **acap-v2** repository, where the new lead programmer <u>discusses the upcoming fixes and improvements</u>.
143145
</Callout>
144146
145147
| Criteria | Purpose | ACAP [1.0](/changelog/#version-1-acap-10) | ACAP [2.0](/changelog/#version-2-acap-20) |

0 commit comments

Comments
 (0)