Status of Certificate Transparency in Android Webview

532 views
Skip to first unread message

Peter Matthews

unread,
Nov 21, 2018, 9:36:17 AM11/21/18
to android-w...@chromium.org
I need to know the state of CT enforcement in the Android Webview used in mobile apps. Does anyone know if the Android Webview is already requiring certificate transparency logs yet or enforcing certificate transparency? If not yet, is there a timeline available? Do the mobile apps have to modify their code to enable it? Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app? Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

Changwan Ryu

unread,
Nov 29, 2018, 6:49:27 PM11/29/18
to matthews...@gmail.com, a...@chromium.org, android-w...@chromium.org
agl@, could you answer this question?

On Wed, Nov 21, 2018 at 6:36 AM Peter Matthews <matthews...@gmail.com> wrote:
I need to know the state of CT enforcement in the Android Webview used in mobile apps. Does anyone know if the Android Webview is already requiring certificate transparency logs yet or enforcing certificate transparency? If not yet, is there a timeline available? Do the mobile apps have to modify their code to enable it? Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app? Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To post to this group, send email to android-w...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/CAF_K6qgpQ5nESdhrXi2-RoOQQWpjHgm%3DBW8hYNcYQ0hL3k5eZg%40mail.gmail.com.

Nate Fischer

unread,
Nov 29, 2018, 7:18:21 PM11/29/18
to Changwan Ryu, matthews...@gmail.com, a...@chromium.org, android-w...@chromium.org
Based on this comment, I suspect CT is not enabled for WebView. But, confirmation would be good--especially since I need to make sure we're doing the right thing for the NetworkService code path :)
Nate Fischer | Software Engineer | ntf...@google.com



Nate Fischer

unread,
Dec 3, 2018, 3:30:19 PM12/3/18
to Changwan Ryu, matthews...@gmail.com, a...@chromium.org, android-w...@chromium.org
We've received confirmation that Certificate Transparency is not currently enabled in WebView.

> If not yet, is there a timeline available?

There is no timeline for this work.

> Do the mobile apps have to modify their code to enable it?

We don't plan to expose this decision to apps. Does your app have a need to control this decision?

> Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app?

I don't know if this is feasible. I can ask around if this is a priority for you.

> Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

I'm not familiar with this tool, and I'm not sure how CT will impact this. I believe you can try the tool with Chrome Desktop; I expect WebView would interact similarly.

---

For those interested in NetworkService (which impacts the near future), we explicitly enforce the same behavior.

Nate Fischer | Software Engineer | ntf...@google.com


Ricardo García Fernández

unread,
Mar 25, 2020, 12:12:50 PM3/25/20
to android-webview-dev, chan...@google.com, matthews...@gmail.com, a...@chromium.org
I can't seem to find good documentation regarding Android WebView and Certificate Transparency. What's the current status by now? Is CT already enabled? If not, is there any timeline already?


On Monday, December 3, 2018 at 2:30:19 PM UTC-6, Nate Fischer wrote:
We've received confirmation that Certificate Transparency is not currently enabled in WebView.

> If not yet, is there a timeline available?

There is no timeline for this work.

> Do the mobile apps have to modify their code to enable it?

We don't plan to expose this decision to apps. Does your app have a need to control this decision?

> Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app?

I don't know if this is feasible. I can ask around if this is a priority for you.

> Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

I'm not familiar with this tool, and I'm not sure how CT will impact this. I believe you can try the tool with Chrome Desktop; I expect WebView would interact similarly.

---

For those interested in NetworkService (which impacts the near future), we explicitly enforce the same behavior.

Nate Fischer | Software Engineer | ntf...@google.com



On Thu, Nov 29, 2018 at 4:17 PM Nate Fischer <ntf...@google.com> wrote:
Based on this comment, I suspect CT is not enabled for WebView. But, confirmation would be good--especially since I need to make sure we're doing the right thing for the NetworkService code path :)
Nate Fischer | Software Engineer | ntf...@google.com



On Thu, Nov 29, 2018 at 3:49 PM 'Changwan Ryu' via android-webview-dev <android-w...@chromium.org> wrote:
agl@, could you answer this question?

On Wed, Nov 21, 2018 at 6:36 AM Peter Matthews <matthews...@gmail.com> wrote:
I need to know the state of CT enforcement in the Android Webview used in mobile apps. Does anyone know if the Android Webview is already requiring certificate transparency logs yet or enforcing certificate transparency? If not yet, is there a timeline available? Do the mobile apps have to modify their code to enable it? Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app? Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview-dev+unsub...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview-dev+unsub...@chromium.org.

Nate Fischer

unread,
Mar 25, 2020, 1:01:57 PM3/25/20
to Ricardo García Fernández, android-webview-dev, Changwan Ryu, matthews...@gmail.com, a...@chromium.org
No update (still no plans for this). We have no documentation on WebView + certificate transparency, but you can "star" crbug/921750.


Nate Fischer | Software Engineer | ntf...@google.com


On Wed, Mar 25, 2020 at 9:12 AM Ricardo García Fernández <ric.g...@gmail.com> wrote:
I can't seem to find good documentation regarding Android WebView and Certificate Transparency. What's the current status by now? Is CT already enabled? If not, is there any timeline already?

On Monday, December 3, 2018 at 2:30:19 PM UTC-6, Nate Fischer wrote:
We've received confirmation that Certificate Transparency is not currently enabled in WebView.

> If not yet, is there a timeline available?

There is no timeline for this work.

> Do the mobile apps have to modify their code to enable it?

We don't plan to expose this decision to apps. Does your app have a need to control this decision?

> Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app?

I don't know if this is feasible. I can ask around if this is a priority for you.

> Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

I'm not familiar with this tool, and I'm not sure how CT will impact this. I believe you can try the tool with Chrome Desktop; I expect WebView would interact similarly.

---

For those interested in NetworkService (which impacts the near future), we explicitly enforce the same behavior.

Nate Fischer | Software Engineer | ntf...@google.com



On Thu, Nov 29, 2018 at 4:17 PM Nate Fischer <ntf...@google.com> wrote:
Based on this comment, I suspect CT is not enabled for WebView. But, confirmation would be good--especially since I need to make sure we're doing the right thing for the NetworkService code path :)
Nate Fischer | Software Engineer | ntf...@google.com



On Thu, Nov 29, 2018 at 3:49 PM 'Changwan Ryu' via android-webview-dev <android-w...@chromium.org> wrote:
agl@, could you answer this question?

On Wed, Nov 21, 2018 at 6:36 AM Peter Matthews <matthews...@gmail.com> wrote:
I need to know the state of CT enforcement in the Android Webview used in mobile apps. Does anyone know if the Android Webview is already requiring certificate transparency logs yet or enforcing certificate transparency? If not yet, is there a timeline available? Do the mobile apps have to modify their code to enable it? Will it be possible to log results without enforcing CT, i.e., is there a way for app developers to detect CT issues with any endpoints without breaking the app? Also, what will happen to ability to use tools like Charles Proxy when CT features are rolled out?

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.

--
You received this message because you are subscribed to the Google Groups "android-webview-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-webview...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/android-webview-dev/561a9f79-95db-4547-9d94-0186c2cc9091%40chromium.org.

Jorge García

unread,
Sep 7, 2020, 10:59:41 AM9/7/20
to android-webview-dev, Nate Fischer, android-webview-dev, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández

Hi,  What's the current status by now? Is CT already enabled?

Matt Rea

unread,
Oct 19, 2020, 5:28:56 PM10/19/20
to android-webview-dev, Jorge García, Nate Fischer, android-webview-dev, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández
Does not sound like there is any plans to implement CT verification on webviews. 

For whoever is listening, we would love this feature! And from searching around on Android slack groups, others would as well.. (ASG #security)

Torne (Richard Coles)

unread,
Oct 20, 2020, 11:17:29 AM10/20/20
to Matt Rea, asymm...@chromium.org, Ryan Sleevi, android-webview-dev, Jorge García, Nate Fischer, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández
The WebView team aren't currently planning to implement this, no. The bug is currently assigned to Devon (cc'ed); Devon and Ryan might have thoughts on what would be needed here.

The main questions here would be:

1) what is the compatibility impact of enabling this for WebView - i.e. how many apps are currently relying on certs that won't pass a CT verification if we just enabled it. Ryan, Devon, is there a UMA metric for this that we can check (or enable in WebView if it's not currently being collected) to get some idea of the scope?

2) would we want/need any API for the app developer to control this - this may depend on what the compatibility impact is. If it looks likely to cause a compatibility issue for a nontrivial number of apps then we may need to provide an API to opt in to the verification, though we could enable it by default for apps that target future OS versions. I'm not sure what other needs there might be here; earlier in the thread one suggestion was a way to enable it in a reporting mode that doesn't block anything yet?

Ryan Sleevi

unread,
Oct 20, 2020, 12:13:06 PM10/20/20
to Torne (Richard Coles), Matt Rea, Devon O'Brien, Ryan Sleevi, android-webview-dev, Jorge García, Nate Fischer, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández
Hi Matthew,

I know it's probably not as "transparent" a decision making process (see what I did there), but Nate's response in 2018 is still correct.

We would encourage you to star the bug mentioned, https://crbug.com/921750 . We do monitor such bugs, and that's the best way to stay updated. There's a number of activities happening behind the scenes, but nothing we'd plan to share publicly at this time.

Matt Rea

unread,
Oct 20, 2020, 12:18:25 PM10/20/20
to android-webview-dev, Matt Rea, Devon O'Brien, android-webview-dev, Jorge García, Nate Fischer, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández, to...@chromium.org, You can't view member email addresses for this group (12)

Thank you for the replies. Understood - it is not a priority for the team right now. We will star the bug

I think an opt-in API makes a lot of sense here. Regardless of the compatibility findings, I don't think it should be enabled for everyone initially (assuming this work ever happens)


"earlier in the thread one suggestion was a way to enable it in a reporting mode that doesn't block anything yet?"
I don't see this suggestion? Am I missing something

Torne (Richard Coles)

unread,
Oct 20, 2020, 12:25:56 PM10/20/20
to Matt Rea, android-webview-dev, Devon O'Brien, Jorge García, Nate Fischer, Changwan Ryu, matthews...@gmail.com, a...@chromium.org, Ricardo García Fernández, You can't view member email addresses for this group (12)
On Tue, 20 Oct 2020 at 12:18, Matthew Rea <matthew...@gmail.com> wrote:

Thank you for the replies. Understood - it is not a priority for the team right now. We will star the bug

I think an opt-in API makes a lot of sense here. Regardless of the compatibility findings, I don't think it should be enabled for everyone initially (assuming this work ever happens)

"earlier in the thread one suggestion was a way to enable it in a reporting mode that doesn't block anything yet?"
I don't see this suggestion? Am I missing something

Ah, it's not quoted in this reply chain, but you can see earlier messages in the thread here: https://groups.google.com/a/chromium.org/g/android-webview-dev/c/M-HYQ8RyceU
Reply all
Reply to author
Forward
0 new messages