Oh no, you're thinking, yet another cookie pop-up. Well, sorry, it's the law. We measure how many people read us, and ensure you see relevant ads, by storing cookies on your device. If you're cool with that, hit “Accept all Cookies”. For more info and to customize your settings, hit “Customize Settings”.

Review and manage your consent

Here's an overview of our use of cookies, similar technologies and how to manage them. You can also change your choices at any time, by hitting the “Your Consent Options” link on the site's footer.

Manage Cookie Preferences
  • These cookies are strictly necessary so that you can navigate the site as normal and use all features. Without these cookies we cannot provide you with the service that you expect.

  • These cookies are used to make advertising messages more relevant to you. They perform functions like preventing the same ad from continuously reappearing, ensuring that ads are properly displayed for advertisers, and in some cases selecting advertisements that are based on your interests.

  • These cookies collect information in aggregate form to help us understand how our websites are being used. They allow us to count visits and traffic sources so that we can measure and improve the performance of our sites. If people say no to these cookies, we do not know how many people have visited and we cannot monitor performance.

See also our Cookie policy and Privacy policy.

This article is more than 1 year old

Chef plugs Ruby vulns with Server release

Always something else you can throw in the pot

Chef pushed version 12.4.0 of its Server out the door this week, and plugged a number of security vulns in the process.

The Mary Berry of config management software vendors said it had updated the version of Ruby on Rails in its oc-id authentication to fix a range of CVEs.

The same update apples to its Management Console, which also gets a security release.

It also announced v1 of Server Admins, which will allow “non-superusers to perform creation, deletion, editing, and listing on all users (except the superuser) in a Chef Server, granting great flexibility around user management.”

Server 12.4.0 also implements Check Authentication Signing Protocol v1.3, which will free users from the tyranny of SHA1 when it comes to digital signatures. Instead it will use SHA256 as the hashing algorithm, which will make it easier to use the platform within certain US government requirements.

You can get the full run-down of changes here.

In a separate posting, Chef noted Open SSL had issued a high severity security advisory, in conjunction with fixes, covering OpenSSL 1.0.2. It said no action was needed, as no Chef products used OpenSSL 1.0.2. ®

 

Similar topics

TIP US OFF

Send us news


Other stories you might like