Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
-
Google @google
- Seattle, WA
- http://mikehelmick.com/
Pinned
605 contributions in the last year
Activity overview
Contributed to
google/exposure-notifications-server,
mikehelmick/exposure-notifications-server-OLD,
mikehelmick/AdventOfCode2019
and 5 other
repositories
Contribution activity
May 2020
Created a pull request in google/exposure-notifications-server that received 13 comments
- log effective environment config on startup. Omit DB password
- default max number of keys should be 15, per e2e testing w/ client team
- pass through empty batches
- ensure a minimum export file length
- complete move of transmission risk to per-exposure key
- make tranismission risk per-exposure key
- [WIP] add remaining config details to export config, denormalize on batch c…
- allow for gaps, ensure no overlaps
- align spec and api implementation.
- Update issue templates
- expand reviewers list
- enforce that intervals are consecutive on upload
- remove ability to accept keys w/ future intervals
- tighten default time for future keys
- add metrics exporter tests
- add metrics
- move to common setup for all servers.
- create a 'common main' and demonstrate with exposure server
- fix 001 down migration, didn't drop type
- allow for an APK to have multiple hashes, test/release keys
- add resolving of secret environment variables back in
- use kelseyhightower/envconfig for environment variable processing
- new nonce calculation
- Validation for publish API
- fix 7 down migration
- Some pull requests not shown.
- Update Terraform setup from Mike's journey
- Add support for Azure KeyVault and HashiCorp Vault interfaces
- Refactor apiconfig interfaces
- Restructure api directories to be under internal matching package name
- Enable vacuum on all tables
- add sample export file
- Update example POST payload
- Adjust batch boundary conditions so that published keys hit an open batch
- Move iOS verification into the database layer
- Actually override database in tests
- Move iOS verification into the database layer
- docker can't mount things in /home
- update to export signing
- Create "dev" script for easier up
- create a 'common main' and demonstrate with exposure server
- Implement client auth for federationpull service.
- Use FederationAuthorization to control access to federation endpoint.
- Refactoring exposure-client. Adding flags for request creation.
- Add initial iOS verification
- Add Test DB Tests to Presubmit
- comment updates for signature fields
- Make secretsDir private, add WithSecretsDir option
- tighten up ownership on the export proto
- Replace TODO Mentions with GitHub user ids
- presubmit location incorrect in readme
- Some pull request reviews not shown.
Created an issue in google/exposure-notifications-server that received 6 comments
- consider application level encryption of key data in the databse
- pad daily downloads to ensure minimunm size
- run VACUUM on postgresql database
- transmissionRisk should be per-key on upload not per-patch
- Create index on exposure.created_at
- Tool to generate export files
- federation clean up
- APIConfig
- Remove verification_authority_name field
- Fix alignment between spec and implemenation
- MCC / ISO country codes
- ExportConfig - include bundle_id / app_package_name in config
- Embargo keys for 2 hours after expiry.
- Determine if keys can have gaps
- ensure keys are consecutive on upload
- ensure logs based metrics appear on all binaries
- implement optional export encryption
- Refactor duplicate code in mains
- support multiple APKHashes per app package
- Add specific field in publish API for roaming
- make server more robust to padded and non-padded base64 encodings
- Implement iOS device check
- bucket name should be part of ExportConfig
- Write client/server interop spec
- put dependencies behind interfaces
- Some issues not shown.
1
contribution
in private repositories
May 11