Strafzölle im Welthandel: Will Trump die liberale Weltordnung kippen?

heise online Newsticker - 29. März 2018 - 6:00
Südkorea ist eingebrochen und hat den USA weitreichende Zugeständnisse beim Handel gemacht. China reagiert mit Gegenmaßnahmen auf die Trumpsche Zollpolitik. Europa schaut vorerst gebannt zu, will sich aber auf keinen Fall von Trump erpressen lassen.

Wunderkraut Sweden Blog: Drupal SA-CORE-2018-002 and us

Planet Drupal - 28. März 2018 - 23:27
One week ago, we got a warning about a very important security update for drupal core, that effected drupal 7 and 8 (and even 6, that is not supported anymore) were going to be released today. And we started to plan for updates. One week ago, we got a warning about a very important security update for drupal core, that effected drupal 7 and 8 (and even 6, that is not supported anymore) were going to be released today. And we started to plan for updates. For a couple of years ago, it was a hard work for us to update a site if a security update was released. Now days our hosting and our processes is much better and simplified, and thanks to the team effort of our Live-team at Digitalist, we got our most important sites patched in minutes after the security release were released.  Totally we patched around 1700 sites that we are hosting in less than 2 hours after the security patch were released. If you… Read More

Platform.sh: More details on Drupal SA-CORE-2018-002

Planet Drupal - 28. März 2018 - 22:00
More details on Drupal SA-CORE-2018-002 Crell Wed, 03/28/2018 - 20:00 Blog

Platform.sh customers should visit Safe from DrupalGeddon II aka SA-CORE-2018-02 for the specific steps we took to protect all our Drupal instances.

Earlier today, a critical remote code execution vulnerability in Drupal 6, 7, and 8 was disclosed. This highly-critical issue affects all Drupal 7.x and 8.x sites and most Drupal 6.x sites. It is trivially exploitable remotely by anonymous users on any site that exposes forms. It is very possible that your site exposes this vulnerability even if you are not aware of publicly accessible forms. You should update immediately any Drupal site you have to versions 8.5.1, 8.4.6, or 7.58, as appropriate.

How to know if I am affected?

We are currently not aware of exploits of this vulnerability in the wild but this will undoubtedly change in the next few hours. Writing an exploit for this is trivial and you should expect automated internet-wide attacks before the day is out.

You should take immediate steps to protect yourself. This is as bad or worse than the previous highly-critical vulnerability SA-CORE-2014-05 that wreaked havoc three and a half years ago affecting more than 12 Million websites.

(Like, seriously, if you are reading this and you are not on Platform.sh or another provider that has put a platform-level mitigation in place, go update your sites and then come back and finish reading. Please. Platform.sh customers, see below for how to quickly update your site.)

Where does the vulnerability come from?

The issue is in Drupal's handling of HTTP request parameters that contain certain special characters. These characters have special meaning in various places in Drupal, which if misinterpreted could lead to unexpected code paths being executed. The solution in the latest patch is to filter out such values before passing them off to application code.

Fortunately that same strategy can be implemented at the network layer. We have therefore applied the same logic to our Web Application Firewall to reject requests containing such values and deployed it across all projects in all regions, both Platform.sh Professional and Platform.sh Enterprise. That should protect all Drupal and Backdrop installations running anywhere on Platform.sh until they are upgraded.

What to do?

You must update any and all Drupal instances with 6.x, 7.x and 8.x or Backdrop CMS, or verify that your hosting provider has put in place an automated mitigation strategy for this vulnerability. (All Platform.sh clients are safe; our new WAF now detects and blocks all variants of this attack). Even if your hosting provider has a mitigation strategy in place you should update immediately anyway.

Drupal 6.x is no longer maintained and unlike Drupal 7.x and 8.x it does not support automated updates. Third-party support providers may provide a patch but you should make plans to upgrade from Drupal 6 to Drupal 8 as soon as possible.

Hopefully you are using Composer for your Drupal 7.x and 8.x or Drush make for Drupal 7.x, as is the default with Platform.sh installations.

To upgrade Drupal via Composer

To update your Drupal instances, and test nothing breaks you can follow the following simple procedure:

Verify that your composer.json file does not lock down drupal core to a minor version it should be something like "drupal/core": "~8.0". Then run:

git checkout -b security_update composer update

Make sure that Drupal Core was updated to 8.5.1 or higher. (Check composer.lock using git diff). Commit and push your changes:

git commit –am ’fix for SA-CORE-2018-02’ && git push

On Platform.sh you can test that everything is fine on your automatically-generated staging environment, then merge to master putting this to production.

If you do not use Platform.sh you should test this either locally or your testing server; and follow your normal procedure to update your live sites.

To upgrade Drupal using Drush Make

If you are using "Drush Make" style of dependency management, again, make sure you are not locked down to a vulnerable version such as:

projects[drupal][version] = 7.57

if it is, bump it up to 7.58. Then make a branch and update it:

git checkout -b security_update drush pm-update

Commit the changes and push the result to Platform.sh for testing. Once you're satisfied nothing is broken merge back to master and deploy.

To upgrade Drupal if you're checking Drupal core into your repository

If you're running a "vanilla" Drupal setup, with all of Drupal checked into Git, the easiest way to upgrade is using drush.

In your local environment, go to your Drupal document root and run:

git checkout -b security_update drush pm-update drupal

Commit the changes and push the result to Platform.sh for testing. Once you're satisfied nothing is broken merge back to master and deploy. Afterward, look into how to migrate your site to a dependency managed configuration, preferably Composer. It will make maintenance far easier and more robust in the future.

As a reminder, your Platform.sh instances are not vulnerable as they are protected by our WAF. You should still apply the fixes ASAP.

Damien Tournoud 28 Mar, 2018

Platform.sh: SA-CORE-2018-002 Drupal core vulnerability: We've got you covered

Planet Drupal - 28. März 2018 - 21:56
SA-CORE-2018-002 Drupal core vulnerability: We've got you covered Crell Wed, 03/28/2018 - 19:56 Blog

An hour ago the SA-CORE-2018-002 critical Drupal vulnerability was disclosed. It was announced a week ago PSA-2018-001. That allowed us to gather our technical team and make sure we can develop and deploy a mitigation to all our clients immediately as the issue is made known.

If you're not running on Platform.sh, please stop reading this post and go update your Drupal site to version 8.5.1 / 8.4.9 / 8.3.8 / 7.58 right now. We're serious; upgrade first and ask questions later.

If you are running on Platform.sh: You're safe and can continue reading... then upgrade.

The vulnerability (also referred to as CVE-2108-7600) affects the vast majority of Drupal 6.x, 7.x and 8.x sites and allows arbitrary remote code execution that allow anonymous remote users to take full control of any affected Drupal site prior to 8.5.1 / 8.4.9 / 8.3.8 / 7.58.

The same issue is present in Backdrop CMS installations prior to 1.9.3.

If your Drupal site is not hosted on Platform.sh we encourage you to immediately update all your Drupal sites to 8.5.1 / 7.58 or to take your site offline. This is serious and trivially exploitable. You can expect automated attacks to appear within hours at most. If you are not on Platform.sh or another provider that has implemented a mitigation your site will be hacked. This is as critical as the notorious “DrupaGeddon” episode from three and a half years ago.

If you are hosting on Platform.sh...

Platform.sh is pleased to announce all Drupal sites hosted on all our regions and all our plans are automatically safe from this attack.

Platform.sh has many security layers that make attacks such as this much harder than on comparable services. Starting from our read-only hosts and our read-only containers, through our auditable and reproducible build-chain, and static-analysis based protective block.

In response to this latest vulnerability, we've taken two important steps:

  1. We've added a new rule to our Web Application Firewall (WAF) on all regions and on all Enterprise clusters that detects and blocks requests trying to exploit this latest attack vector, even if your site hasn't been updated. (But still, please update.)

  2. We are adding a check to our protective block to prevent deployment of affected Drupal versions. If you try to push an insecure Drupal version our system will flag it for you and warn you that you are pushing known-insecure code. Please update your code base as soon as possible.

As a client if you need any further assistance or want more information about the vulnerability, how it may affect you, and our mitigation strategy don’t hesitate to contact support. We have set our WAF to an especially aggressive stance for now and this may result in some users seeing a "400 Bad Request" message in some edge cases for legitimate traffic. If you experience this, please contact our support immediately they will be able to help.

Ori Pekelman 28 Mar, 2018

Pantheon Blog: Security Update: Drupal SA-2018-002

Planet Drupal - 28. März 2018 - 21:28
The Drupal Security Team has published Drupal SA-2018-002 to address a critical vulnerability. This the first update of this magnitude since SA-2014-005 (aka “Drupageddon”) back in 2014. In that case, the time from release to automated exploitation was around seven hours.

myDropWizard.com: HIGHLY CRITICAL Drupal core security update for SA-CORE-2018-002 (including Drupal 6!)

Planet Drupal - 28. März 2018 - 21:25

Today, there is a Highly Critical security release for Drupal core to fix a Remote Code Execution (RCE) vulnerability. You can learn more in the security advisory:

Drupal core - Critical - Remote Code Execution - SA-CORE-2018-002

As we noted last week, this issue also affects Drupal 6! So, we're also making a Drupal 6 Long-Term Support (D6LTS) release of Drupal core.

Drupal 6 core security update

As you may know, Drupal 6 has reached End-of-Life (EOL) which means the Drupal Security Team is no longer doing Security Advisories or working on security patches for Drupal 6 core or contrib modules - but the Drupal 6 LTS vendors are and we're one of them!

Here you can download the Drupal 6 patch to fix, or a full release ZIP or TAR.GZ.

If you have a Drupal 6 site, we recommend you update immediately! We have already deployed the patch for all of our Drupal 6 Long-Term Support clients. :-)

If you'd like all your Drupal 6 modules to receive security updates and have the fixes deployed the same day they're released, please check out our D6LTS plans.

Note: if you use the myDropWizard module (totally free!), you'll be alerted to these and any future security updates, and will be able to use drush to install them (even though they won't necessarily have a release on Drupal.org).

Security advisories: Drupal core - Highly critical - Remote Code Execution - SA-CORE-2018-002

Planet Drupal - 28. März 2018 - 20:14
Project: Drupal coreDate: 2018-March-28Security risk: Highly critical 21∕25 AC:None/A:None/CI:All/II:All/E:Theoretical/TD:DefaultVulnerability: Remote Code Execution Description: 

CVE: CVE-2018-7600

A remote code execution vulnerability exists within multiple subsystems of Drupal 7.x and 8.x. This potentially allows attackers to exploit multiple attack vectors on a Drupal site, which could result in the site being completely compromised.

The security team has written an FAQ about this issue.

Solution: 

Upgrade to the most recent version of Drupal 7 or 8 core.

  • If you are running 7.x, upgrade to Drupal 7.58. (If you are unable to update immediately, you can attempt to apply this patch to fix the vulnerability until such time as you are able to completely update.)
  • If you are running 8.5.x, upgrade to Drupal 8.5.1. (If you are unable to update immediately, you can attempt to apply this patch to fix the vulnerability until such time as you are able to completely update.)

Drupal 8.3.x and 8.4.x are no longer supported and we don't normally provide security releases for unsupported minor releases. However, given the potential severity of this issue, we are providing 8.3.x and 8.4.x releases that includes the fix for sites which have not yet had a chance to update to 8.5.0.

Your site's update report page will recommend the 8.5.x release even if you are on 8.3.x or 8.4.x. Please take the time to update to a supported version after installing this security update.

This issue also affects Drupal 8.2.x and earlier, which are no longer supported. If you are running any of these versions of Drupal 8, update to a more recent release and then follow the instructions above.

This issue also affects Drupal 6. Drupal 6 is End of Life. For more information on Drupal 6 support please contact a D6LTS vendor.

Reported By: Fixed By:  Contact and more information

The Drupal security team can be reached by email at security at drupal.org or via the contact form.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Eine Milliarde Euro Beute mit Malware Carbanak und Cobalt: Polizei schnappt mutmaßlichen Bandenführer

heise online Newsticker - 28. März 2018 - 19:00
In Spanien wurde der mutmaßliche Kopf einer kriminellen Organisation verhaftet, die mit Hilfe von Schadsoftware insgesamt über eine Milliarde Euro erbeutet haben soll.

E-Mail-Verschlüsselung: Enigmail 2.0 ist da

heise online Newsticker - 28. März 2018 - 19:00
Mit der neuen Enigmail-Version 2.0 für den Mail-Client Thunderbird kann man unter anderem neben Text in Mails nun auch die Betreffzeile verschlüsseln.

Drupal core announcements: FAQ

Planet Drupal - 28. März 2018 - 18:50

this is a faq

ThinkDrop Consulting: Newest version of DevShop eases Drupal update and release process.

Planet Drupal - 28. März 2018 - 18:15
Newest version of DevShop eases Drupal update and release process. Jon Pugh Wed, 03/28/2018 - 12:15

In just a few hours, the first serious critical security update for Drupal since "Drupalgeddon" will be released.

To make this update easier for DevShop users, we've pushed out a new release with 2 features that allow you to update your sites without ever leaving your web browser: "Update, Commit & Push" and "Tag a Release".

"Commit & Push"

The "Update Drupal" button has been available in DevShop for some time, but now you can automatically commit the results by checking a box.

Acro Media: Custom Product Pages in the UH+ Drupal Commerce 2 Demo

Planet Drupal - 28. März 2018 - 17:18

Acro Media recently launched a demo ecommerce site called Urban Hipster that exhibits the incredible range of out-of-the-box functionality you get with Drupal Commerce 2 (check it out here). To make the demo even more amazing, we've also created a “Plus” version that shows you what's possible with a bit of extra work.

Some background

If you have an ecommerce business or have a product that you're trying to sell online, a product catalog could be just what you need. But if you produce your own product or you only have a few different products, a product showcase is actually a better way to demonstrate and sell your wares. It's like buying something on Amazon vs buying something on Apple: Amazon has an enormous list of products and all the pages look the same, whereas Apple has fully customized, unique pages for each item it sells.

UH Axe builder product page

When you go to buy the UH Axe on the demo, you'll bring up a unique UH Axe builder product page in the Apple style. The page talks about what the UH Axe is and what its purpose is, and then you're able to choose the type of handle you want, the handle length, how heavy the axe head should be, whether you want a sheath, etc. By the time you add it to your cart, it has become a completely unique product with all the variations that you've chosen. But it exists and is configured the same way that any other product would.

It's actually a very similar configuration as the White and Wood Chair example on the demo; it just looks completely different.

The functionality behind a lot of the extra content is a module called Paragraphs. It's similar to Panels (which a lot of people use), but a bit simpler and more streamlined. It doesn't have the same breadth of functionality, but it's easier to work with, and it lets you do all those customizations like deciding where you want to put it on the page and so on. It looks very custom, but it is surprisingly configurable through the back end.

(A note of caution: while it's mostly out-of-the-box functionality, some of the more complex design elements did require a bit of custom code. That’s why it’s on the “Plus” demo.)

Keep in mind that it's not uncommon to have both ways of viewing the product: a fancy customized page as well as a more standard catalog. People can get to the product through either route.

The bottom line

You can make awesome product pages through Drupal Commerce without a lot of effort.

 

More from Acro Media Chat with us

If you'd like a personalized tour to discuss how Drupal Commerce fits into your ecommerce solution, give us a shout. We're happy to show and tell.

Mobomo: Key Drupal Taxonomy: Part 1

Planet Drupal - 28. März 2018 - 16:26

When it comes to considering what is the best CMS for a website, most don’t know up from down or Drupal from WordPress. At Mobomo, we consider ourselves Drupal experts and have guided many of our clients through a Drupal migration. Drupal is a content management system that is at the core of many websites.  Drupal defines itself as “an open source platform for building amazing digital experiences.” These simple definitions make it sound easy, but it can in fact be very confusing. Listed below are some popular terms defined to help make the start of the migration process what it should be, simple and easy:

  1. Taxonomy – classification system.  In WordPress, this system is very similar to the Categories you’ll find in that CMS.
  2. Vocabularies – a category, or a collection of terms.
  3. Terms – items that go inside a vocabulary.
  4. Tags – generic way to start classifying your content (this is the default).
  5. Menus – refers both to the clickable navigational elements on a page, and to Drupal’s internal system for handling requests. When a request is sent to Drupal, the menu system uses the provided URL to determine what functions to call.  
    • There are 4 types:
      • Main
      • Management
      • Navigation
      • User
  6. Theme – look and feel of a site, determined by a combined collection of template files, configuration files and asset files (JavaScript, CSS, images, fonts). A theme contains elements such as the header, icons, block layout, etc. Drupal modules define themeable functions which can be overridden by the theme file. There are additional themes available in the themes section of downloads.
  7. Content Type – Every node belongs to a single “node type” or “content type”, which defines various default settings for nodes of that type, such as whether the node is published automatically and whether comments are permitted. Common “Content Types” that just about any website would have include: blog post and page. Content types can have different fields and modules can define their own content types. The core Drupal Book and Poll modules are two examples of modules that define content types
  8. Fields – Elements of data that can be attached to a node or other Drupal entities. Fields commonly contain text, image, or terms.
  9. Node – A piece of content in Drupal, typically corresponding to a single page on the site, that has a title, an optional body, and perhaps additional fields. Every node also belongs to a particular content type, and can additionally be classified using the taxonomy system. Examples of nodes are polls, stories, book pages and images.
  10. Views – module that lets gives you a click and configure interface for running database queries. It can output the results in a variety of formats.
  11. Views Display – created inside of a view to display the objects fetched by the view in different manners.
  12. Module – Code that extends Drupal features and functionality (but doesn’t provide the HTML markup or styling of a theme). Drupal core comes with required (pre-installed) modules and some which are optional. Thousands of non-core or “contrib” modules are listed in the project directory.
    • Core- features that are available within Drupal by default
    • Custom- modules that are developed for a specific purpose that are not available within Drupal Core
    • Contributed- after custom modules are created by Drupal developer, they are often made available to others within the Drupal community. There are more than 40,000 modules available today.

The post Key Drupal Taxonomy: Part 1 appeared first on .

Facebook bevorzugt lokale Nachrichten nun weltweit

heise online Newsticker - 28. März 2018 - 16:00
In den Newsfeeds der Facebook-Nutzer sollen künftig mehr lokale Nachrichten zu lesen sein. Diese Bevorzugung galt zunächst nur für die USA – jetzt gilt sie weltweit.

Acquia Developer Center Blog: Checking for Bad Passwords in Drupal to Avoid Site Compromise

Planet Drupal - 28. März 2018 - 15:42

Easy-to-guess passwords are all too often the means by which intruders gain unauthorised access. It's useful to be able to audit the passwords in use on your site - especially for user accounts with administrative privileges.

Ideally your Drupal site should have a robust (but user friendly) password policy (see my previous post: Password Policies and Drupal). However, this is not always possible.

Tags: acquia drupal planet

InternetDevels: 17 social media integration modules for Drupal 8

Planet Drupal - 28. März 2018 - 15:39

Audience boosters, sales increasers, brand builders… All this and more applies to social networks! Drupal lets you easily integrate these unmatched promotion tools with your website. We have shared a great collection of Drupal social media integration modules in part 1 and 2.

Read more

Statt Lochkarten: Servos steuern eine alte Spieluhr

heise online Newsticker - 28. März 2018 - 15:30
Die Pappkarten einer Lochkarten-Spieluhr machten Probleme. Die typische Lösung eines Makers: weg mit dem Papier, her mit Servo-Motoren, Mikrocontroller und MIDI.

Microsoft bringt Browser Edge aufs iPad

heise online Newsticker - 28. März 2018 - 15:30
Nach mehreren Monaten hat Microsoft die Mobilversion des Browsers für Tablets angepasst und verspricht ein gutes Zusammenspiel mit Windows 10. Zur Produktverbesserung möchte der Hersteller gerne den Browser-Verlauf einsehen.

Rancher 2.0 im Test: Round-up der Kubernetes-Herde

heise online Newsticker - 28. März 2018 - 15:30
Mit Version 2.0 aktualisiert Rancher seine Cluster-Verwaltungsplattform. Insbesondere Kubernetes haben die Entwickler nun tief in ihre Software integriert.

Atari VCS: Neue Infos zur modernen Retro-Spielekonsole

heise online Newsticker - 28. März 2018 - 15:00
Bei einem Besuch bei Atari in San Francisco haben wir die neue Retro-Spielekonsole Atari VCS in die Hände genommen. Was final neben einer AMD-APU drin stecken wird, steht aber immer noch nicht ganz fest.