Discourse 2.4.0.beta9 introduces several new features and security enhancements. Users can now feature a topic on their profile, visible on their user card and profile page via Preferences. Security improvements include removing unsafe-eval from the Content Security Policy (CSP), hashing API keys in the database for better auditability and leak protection, and moving Internet Explorer support into a core plugin ahead of its official deprecation in June 2020. A warning is now shown if a theme component is installed but not added to a theme. The release also includes 6 security fixes reported via community and HackerOne, such as correcting permission checks for API key revocation and upgrading dependencies like rack-mini-profiler and puma. Plugin updates cover BCC, Data Explorer, RSS Polling, Voting, Solved, Docker Manager (with a security fix), GitHub, User Notes, Group Tracker (UX improvements), Sitemap, Policy, Calendar (enhanced holiday display, timezone logic, performance), Encrypt, and Logster (custom grouping support). Additional features include reordered nested categories, password mismatch alerts in rake admin:create, and a setting to remove the X-Frame-Options header. Bug fixes span IE11 compatibility, tag and category handling, upload and composer behavior, and various UI regressions. UX improvements focus on category styling, post menus, mobile tap areas, and alignment of social login buttons. jomaxro and jomaxro detail these changes, noting that the full list of updates exceeds what can be summarized here.
Users can now select a topic they wish to feature on their profile. The topic will appear on their user card, as well as on their profile page. Users can add a topic from their Preferences, Profile tab.
We’re always looking for ways we can make Discourse even more secure. Late last year we added support for Content Security Policy to Discourse. CSPs help mitigate XSS attacks, one of the most common web vulnerabilities. In order to fully support existing Discourse features and plugins, we included the unsafe-eval directive. We’ve now removed all usage of eval() from Discourse in production, as well as our official plugins, so we’ve removed unsafe-eval from our CSP, making our CSP even stricter.
Hash API keys in the Database
API keys are now only visible when first created. After that, only the first four characters are stored in the database for identification, along with an sha256 hash of the full key. This makes key usage easier to audit, and ensures attackers would not have access to the live site in the event of a database leak.
Move Internet Explorer support to core plugin
Discourse will be dropping support for Internet Explorer in June 2020. (A formal announcement will be made mid-January). In preparation for this, Internet Explorer specific code has been moved into a plugin, making it easier to remove come June.
Warning when theme component is installed but not added to a theme
When creating or installing a theme component, users may forget that it needs to be added to a theme in order to become active. After the initial creation/installation only, users will be warned should they attempt to navigate away from the theme component without first adding it to a theme.
But wait, there’s more! We do our best to highlight new features and changes for you, but there’s always too many changes to detail. For a full list of new features, bug fixes, UX improvements, and more, be sure to review the Additional Features and Fixes listed below.
Security Updates
This beta includes 6 security fixes for issues reported by our community and HackerOne.
Correct permission check when revoking user API keys