Opened 16 months ago

Closed 3 weeks ago

#2140 closed defect (no response)

Android NPE i2ptunnel SSL client

Reported by: zzz Owned by: meeh
Priority: minor Milestone: n/a
Component: apps/android Version: 0.9.32
Keywords: Cc: str4d
Parent Tickets:

Description

<i2pr> [Slack/str4d] zzz, I've spotted one NPE that might be relevant to you (has only happened three times in the last release cycle)
<i2pr> [Slack/str4d] SelfSignedGenerator?.generate(), line 172, call to cert.checkValidity()
<i2pr> [Slack/str4d] throws a NPE inside com.android.org.conscrypt.NativeCrypto?.ASN1_TIME_to_Calendar
<i2pr> [Slack/str4d] called from com.android.org.conscrypt.OpenSSLX509Certificate.getNotBefore()
<i2pr> [Slack/str4d] The traceback (can't paste, looking at this on my phone) is from saving a tunnel, which in background calls GeneralHelper?.updateTunnelConfig(), which triggers SSLClientUtil.createKeyStore
<i2pr> [Slack/str4d] (which then calls KeyStoreUtil?.createKeys, leading to the above NPE)
<zzz> str4d, that would only be if somebody enabled SSL on a client tunnel. just tried it on android and desktop, no problems
<zzz> and the desktop certificate looks fine with certtool
<zzz> public static native void ASN1_TIME_to_Calendar(long asn1TimeCtx, Calendar cal);
<zzz> so it's not working on the cert at all, seems unlikely to be our fault?

Subtickets

Change History (4)

comment:1 Changed 14 months ago by meeh

  • Milestone changed from 0.9.34 to 0.9.35

comment:2 Changed 14 months ago by meeh

  • Owner changed from str4d to meeh
  • Status changed from new to assigned

comment:3 Changed 8 months ago by zzz

  • Cc str4d added
  • Status changed from assigned to infoneeded

str4d or meeh, please paste the full traceback from 8 months ago

comment:4 Changed 3 weeks ago by zzz

  • Milestone changed from 0.9.35 to n/a
  • Resolution set to no response
  • Status changed from infoneeded to closed

SSL disabled in android, see #2296
so this ticket no longer relevant.

meeh reports that only 60 days of crash reports are available in gplay
In the future we need full stack traces for all gplay tickets immediately so this doesn't happen again

Note: See TracTickets for help on using tickets.