Skip to content

Promote stages/rc-2017-10-02 to staging#1701

Merged
zachmargolis merged 35 commits intostages/stagingfrom
stages/rc-2017-10-02
Sep 28, 2017
Merged

Promote stages/rc-2017-10-02 to staging#1701
zachmargolis merged 35 commits intostages/stagingfrom
stages/rc-2017-10-02

Conversation

@zachmargolis
Copy link
Contributor

No description provided.

zachmargolis and others added 30 commits August 31, 2017 15:43
**Why**: To prevent requests from taking forever
**Why**: The values are untrusted
**Why**: So that when a user resends a letter, it does not invalidate
the USPS confirmation code in preceding letters. This means that if a
user resends a letter before receiving their first letter, the code in
the first letter can still be used to verify their account.

**How**: This commit adds a new model named `UspsConfirmationCode`. This
model is associated with a profile and has an asymmetrically encrypted
OTP. When the user enters an OTP, the record with the matching OTP
fingerprint is found. This is used to determine whether the entered OTP
is valid for verifying their account.
…attributes

Allow multiple USPS confirmation codes
Redact more phone numbers in error messages
Keep locale when cancelling SP-initiated signup
…ithout-cron

Revert "Remove cron dependency for worker health checker"
**Why**: To make sure the correct class is called each time. Otherwise,
a class that was set by a previous spec will still be in effect for the
next test, but might be the wrong class for that test.
**Why**:
- Those gems are not required to allow people outside of 18F to run the
app locally. In some cases, like the equifax gem, they are preventing
those folks from running the app.
Ignore production and deploy gems for local dev
**Why**: It looks like we may need to move away from Mailchimp for
compliance reasons. SES is an email service we can buy from AWS to fill
the gap.
Change prod emails from mailchimp to SES
**Why**: Malformed host headers cause exceptions
Remove HTTP Host header entirely
**Why**: Bad input should not cause us to throw exceptions
**Why**: Rack encodes headers into 8 bit ASCII which results in encoding
compadibility errors futher down the stack when the app tries to
manipulate them. This commit encodes the headers and replaces
incompatible characters with `?` characters so the headers do not cause
the app to respond with 500s.
Sanitize UTF8 characters from headers
Change the .ruby-version file to use `2.3` rather than `2.3.3`. This
may require users to create an alias in their ruby version config to
specify a particular point release.

For example, in rbenv you would create a symlink from `2.3` to `2.3.5`.
If you're using ruby-build and have rbenv-aliases installed, this will
happen automatically when you install new versions of ruby.

- https://github.com/tpope/rbenv-aliases

Also update the version in the Dockerfile and CircleCI config to not pin
to a specific point release.

This has no impact on login.gov servers, which don't use the
.ruby-version file. The Gemfile already allows any 2.3.* release after
2.3.3.
Set all existing migrations as being from Rails 4.
monfresh and others added 3 commits September 18, 2017 11:18
Allow running any Ruby 2.3 version, upgrade to latest.
**Why**: For a better user experience.
Copy link
Contributor

@jmhooper jmhooper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, but do we want to add the commits to disable international voice calling?

@zachmargolis
Copy link
Contributor Author

@jmhooper which PRs are those? I can consider cherry-picking those on I guess :/

@jmhooper
Copy link
Contributor

Disable international voice dialing

(cherry picked from commit 26c9202)
Enable voice calling to Mexico

(cherry picked from commit 657c442)
@zachmargolis
Copy link
Contributor Author

@jmhooper I cherry-picked those two PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants