happy bmo push day!

release tag

the following changes have been pushed to bugzilla.mozilla.org:

  • [1459336] feed daemon skips setting r+ for accepted revision if the same user already has a flag set even if flag is status of ?
  • [1460466] Phab bot does not create r+ for acceptance when there are still blocking reviewers
  • [1440086] Refactor PhabBugz extension code to use new User.pm module for better type checking
  • [1458664] Feed daemon when adding or updating a new project in Phabricator, it should fix permissions and also make sure phab-bot is project member
  • [1462686] Current phabbugz in bmo master still refers to get_phab_bmo_ids() which is no longer part of the code
  • [1461819] Plack::Handler::Apache2 accidentally unsets $ENV{MOD_PERL}
  • [1461400] Log errors in webservices when undef values are passed to $self->type()

discuss these changes on mozilla.tools.bmo.

Changes to Secure Bugmail on bugzilla.mozilla.org

There’s a big change coming on May 16th, 2018:

We’ve replaced the encryption code for secure bugmail.
All OpenPGP-formatted bugmail will be encrypted using the openpgp.js library.
There are no changes to the S/MIME encryption, and if you’re already using S/MIME my recommendation is to continue using it.

There are upsides (such as a new feature and several bugfixes) and only a single downside to this change.

Upsides

  • Feature: Messages may be encrypted using the Elliptic curves P-256, P-384, P-521, SECP-256k1, Curve25519, and Ed25519 (You can generate ECC keys with the command gpg --expert --full-gen-key and choosing option 9)
  • Fix Bug 790487: Messages will be encrypted to subkeys when possible.
  • Fix Bug 1190749: Messages will be encrypted using AES256, instead of CAST 5
  • Fix Bug 1256321: Messages will not be encrypted with expired keys.

Future Upsides

In addition to these changes, future work may allow:

  • Generating and receiving wild card key IDs in public-key encrypted session key packets.
  • Experimental opt-in authenticated encryption (AES-EAX, OCB, or GCM) based on the IETF proposal

The Downside

There are a few users whose keys will not work for various reasons.
If you’re one of those users, you can expect an email today (May 11th) explaining your options.

Questions

In anticipation of questions that may be asked, here are some answers.

Why OpenPGP.js?

  • Using gpg is difficult because its API is based on executing processes and communicating over 4 (or perhaps more) file descriptors.
  • Using gpg is also stateful because it must maintain its own key database.
  • Our existing OpenPGP library, while considered the second-most-complete OpenPGP implementation, hasn’t been actively maintained in a while. ProtonMail is actively maintaining OpenPGP.js since 2016, and this inspires confidence.
  • OpenPGP.js has undergone two complete security audits from Cure53. The first audit is available for review.

Will my GPG key work?

Probably. If not, you’ll be hearing from me.

If you would like to check your own key, you can use this baroque single page app to see what keys OpenPGP.js supports.

happy bmo push day!

release tag

the following changes have been pushed to bugzilla.mozilla.org:

  • [1450325] Update email templates with instructions for unsubscribing from all emails
  • [1451599] Checkbox for agreement terms at create account page should be on the left side
  • [1438205] Preserve comments in progress across page reloads
  • [1452531] PhabBugz code should add allow visibility to reviewers when creating custom policies
  • [1440828] Phabricator review requests should show up on the BMO dashboard
  • [1452241] Improve feed error handling and logging
  • [1453124] extensions/PhabBugz/bin/update_project_members.pl should be combined with the normal feed daemon
  • [1455493] cleanup push connector logging
  • [1427395] Allow request_cache to be constant-folded in Bugzilla.pm
  • [1455772] Label bug bounty form credit fields
  • [1373280] Highlight private comments in new bug modal UI
  • [1430367] Ssl preconnect google analytics
  • [1456529] Support SameSite attribute on session cookies
  • [1441732] Improve missing module error in Bugzilla::Extensions and catch more compile errors in tests
  • [1457031] When a revision does not have an bug id, the bug is made public but we also need to remove secure-revision tag

discuss these changes on mozilla.tools.bmo.

Happy BMO Push Day!

Dave's Ramblings

release tag

the following changes have been pushed to bugzilla.mozilla.org:

  • [1450283] JobQueue should treat “no jobs” as a trace-level message, and all other logs as info
  • [1450920] Instant Search doesn’t work when not logged in
  • [1447028] Add auth delegation test script
  • [1446431] Allow Baseline scan to ignore forms that dont need CSRF Tokens
  • [1450791] SES handler needs to support both “event” and “notification” messages (to handle complaint messages in production)
  • [1449282] Create an endpoint that will report back the number of jobs currently in the jobqueue
  • [1450679] Replace custom Sentry integration with Logging
  • [1328900] Create new group called ‘disableusers’ that can only edit the bugmail and disabledtext fields of a user
  • [1450990] Refactor a bunch of the logging config files
  • [1451416] Bugzilla sometimes sends emails to accounts when it shouldn’t

View original post 88 more words

Bugzilla Harmony Beta

In addition to the Mojolicious ❤️, we’re also focused on more near-term gains.
Specifically getting the Bugzilla/Harmony branch running under PSGI, and being a thing you can download and use.

I am happy to announce today that the master branch is in a beta-quality state as of today,

At the moment, the following installation scenarios have been tested:

  • checkout the code
  • run cpanm --installdeps --notest --with-feature=bmo -l local .
  • run checksetup.pl and edit localconfig to point your database (only mysql is currently working)
  • run app.psgi, optionally with starman

If you would like to help the project, a good place to start would be testing this on your systems and reporting back findings.

The next milestone will be integration of the Mojolicious work currently going on in PR #517 in the bmo repo

happy bmo push day!

release tag

the following changes have been pushed to bugzilla.mozilla.org:

  • [1448681] Bugmail Message-ID header format changed without changing In-Reply-To/References, breaking threading
  • [1440829] Bugzilla comment for Phabricator commit should include entire commit message, not just first line
  • [1449413] Refactor circleci container building stuff
  • [1449156] Bugzilla::Memcached should use smaller timeouts and ping servers at instantiation time
  • [1449168] Remove warning –function from jobqueue worker
  • [1441063] Misleading bugzilla comment when asking for re-review
  • [1200695] API-key-creation emails should reflect if the action was a result of auth delegation
  • [1450008] documentation link in API errors is wrong
  • [1450010] The jobqueue supervisor’s pidfile should not be stored in the data directory
  • [1441897] Improve opengraph metadata for bug pages
  • [1447027] Document and tweak vagrant vm to support testing emails
  • [1441244] prevent compounding error messages in tests
  • [1450343] Make the SES handler use Bugzilla::Logging and log more details

discuss these changes on mozilla.tools.bmo.