Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N notebook
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mark Stevens
  • notebook
  • Wiki
  • tablet hardening

tablet hardening · Changes

Page history
mstevens created page: tablet hardening authored Mar 23, 2017 by Mark Stevens's avatar Mark Stevens
Hide whitespace changes
Inline Side-by-side
Showing with 4 additions and 4 deletions
+4 -4
  • tablet-hardening.md tablet-hardening.md +4 -4
  • No files found.
tablet-hardening.md
View page @ 646f62e6
## Tablet Hardening process # Tablet Hardening process
In the development environment, builds are not required to be release builds. In the development environment, builds are not required to be release builds.
Development Environment Development Environment
+ It is required that all key information is removed from logging calls. + It is required that all key information is removed from logging calls.
Production apk builds for tablets are built in release mode: ## Production apk builds for tablets are built in release mode:
+ Debugging flag is disabled + Debugging flag is disabled
+ Proguard rules are standardized + Proguard rules are standardized
+ required that apk methods and classes are obfuscated + required that apk methods and classes are obfuscated
+ all unused classes and methods are stripped + all unused classes and methods are stripped
+ apks are signed with a buzztime release keystore (not the android sdk default keystore) + apks are signed with a buzztime release keystore (not the android sdk default keystore)
APK deployment : ## APK deployment :
Apks deployed to tablets are managed through a package manifest delivered through a SOAP request. Apks deployed to tablets are managed through a package manifest delivered through a SOAP request.
+ Apk's that are not whitelisted or present in the manifest are removed from the tablet. + Apk's that are not whitelisted or present in the manifest are removed from the tablet.
+ Apk's in the manifest are securely downloaded and installed. + Apk's in the manifest are securely downloaded and installed.
+ Apk's in the com.buzztime package space must be signed with the buzztime release keystore + Apk's in the com.buzztime package space must be signed with the buzztime release keystore
Runtime validations and security measures: ## Runtime validations and security measures:
+ Tablets do not enable ADB or USB modes at startup and only enable it if the tablet is associated with a site that is configured to allow it. + Tablets do not enable ADB or USB modes at startup and only enable it if the tablet is associated with a site that is configured to allow it.
+ The Buzztime Core package declares special permissions which may be used by applications to require that Intent, Service and ContentProvider requests are made only by buzztime signed applications. + The Buzztime Core package declares special permissions which may be used by applications to require that Intent, Service and ContentProvider requests are made only by buzztime signed applications.
+ SSL HTTP client requests are configured to use TLS 1.2 and the allowed cipher list is pruned to remove all ciphers that have been identified as insecure. + SSL HTTP client requests are configured to use TLS 1.2 and the allowed cipher list is pruned to remove all ciphers that have been identified as insecure.
......
Clone repository
  • branch code plan
  • build and test configuration
  • build artifact versioning
  • build server instrumented testing
  • build server move
  • bzt16wifi02 releases
  • bzt18uxa02 releases
  • configuration settings and permissions
  • create a repo from cli in gitlab
  • engineering status
  • feature deployment
  • gitlab installation instructions
  • Home
  • ota update and deployment
  • qbert implementation
View All Pages