Bluetooth-Lücke: Patch für "smartes" Vorhängeschloss Tapplock

heise online Newsticker - 27. Juni 2018 - 11:30
Sicherheitsforscher knacken das Schloss Tapplock über Bluetooth in wenigen Sekunden. Auch rohe Gewalt kann das Schloss unter Umständen öffnen.

Mobil-Browser: Edge integriert Adblock Plus

heise online Newsticker - 27. Juni 2018 - 11:00
Der Edge-Browser für Android und iOS hat "Adblock Plus" bereits eingebaut. Noch dürfen ihn aber nur Beta-Tester ausprobieren.

Dresdner Forscher überlisten Tracking-Punkte bei Laserdruckern

heise online Newsticker - 27. Juni 2018 - 11:00
Mit einzelnen gelben Punkten verraten Laserdrucker viel über einen Ausdruck. Zwei Forscher haben die Methode analysiert und ein Gegenmittel gefunden.

Platooning: Vernetzte Lkw-Konvois starten Alltagsbetrieb auf der A9

heise online Newsticker - 27. Juni 2018 - 11:00
Auf der A9 sind nun Lkw unterwegs, die mit einer so genannten elektronischen Deichsel miteinander verbunden sind.

Online-Handel: Marktplätze wollen bei gefährlichen Produkten schneller reagieren

heise online Newsticker - 27. Juni 2018 - 10:30
AliExpress, Amazon, eBay und Rakuten wollen effektiver gegen verbotene Produkte vorgehen. Die EU-Kommission fordert andere Plattformen auf, sich anzuschließen.

Karriere machen in der IT-Branche: Jobmesse zur Cyber Security Challenge Germany

heise online Newsticker - 27. Juni 2018 - 10:30
Im Rahmen der CSCG, dem Finale für Deutschlands beste Hacker, findet am 4. Juli 2018 in Düsseldorf eine Jobmesse für Nachwuchskräfte in der IT-Sicherheit statt.

Mario Tennis Aces angespielt: Grand Slam

heise online Newsticker - 27. Juni 2018 - 10:00
Nintendo lässt mit Mario Tennis Aces die Schläger qualmen. So einfach kann Spielspaß sein.

eHealth: Unternehmen fordern weniger Datensparsamkeit

heise online Newsticker - 27. Juni 2018 - 9:30
Industrieverbände wollen mit einem "Zielbild eHealth" sicherstellen, dass der Aktionsplan eHealth der Bundesregierung innovative Datennutzungen gestattet.

Maschinenbau: Arbeitskräftemangel behindert Produktion

heise online Newsticker - 27. Juni 2018 - 9:30
Im April klagten mehr als ein Drittel der Maschinenbau-Unternehmen über Produktionsbehinderungen durch einen Mangel an qualifizierten Mitarbeitern.

heykarthikwithu: Sites Still Vulnerable to Drupalgeddon 2

Planet Drupal - 27. Juni 2018 - 9:25
Sites Still Vulnerable to Drupalgeddon 2

Attackers are exploiting Drupalgeddon 2 critical vulnerability in Drupal to compromise systems & secretly turn them into malicious cryptocurrency mining machines like cryptojacking malware, mine for Monero.
The only side effects a victim might notice is that their system is running slower or doing more work than usual.

heykarthikwithu Wednesday, 27 June 2018 - 12:55:39 IST

Drupal Europe: Drupal Europe 2018: Digital transformation and enterprise

Planet Drupal - 27. Juni 2018 - 9:04
Photo by Floriane Vita on UnsplashWhat is digital transformation?

It is 2018 and we are still talking about digital transformation? Wasn’t that finished and done ten or fifteen years ago? Not completely. Based on the study from Grand View Research the global digital transformation market size was valued at $177.27 billion in 2017 and is expected to reach $798.44 billion by 2025. It seems like we have just started and a business that does not join the movement will be left behind.

But what is digital transformation? We see it as the integration of digital technology into all areas of a business, resulting in fundamental changes to how businesses operate and how they deliver value to customers. This new approach to customer experience through digital experience is where a platform like Drupal fits in perfectly.

Digital transformation and Drupal

To build connected, omnichannel customer experiences, the technology must have a built in way to support communication between channels, such as physical locations, ecommerce, mobile applications, and social media. Drupal 8 provides APIs for creating solutions and is definitely not limited to being a website platform. With this approach, the ability to engage customers through multiple channels at the same time has become a reality. Enterprises like Bayer, who evaluated and chose Drupal as their preferred platform in November 2017, have embraced the idea of embarking on the digitalization journey with an open source software that has been around for almost two decades and has a clear vision to become the world’s leading omnichannel customer experience solution.

Europe’s biggest Drupal event in 2018

Drupal Europe will be the largest conference in Europe happening in 2018. Drupal Europe organizes the program and session selection process around industry verticals. These focus on usage of Drupal in real life scenarios, in specific target industries, alongside space to cover cutting edge technologies. Digital transformation has become an important movement and the Drupal community has recognized that and dedicated a track to it.

The track provides unique networking opportunities with — and expert advice by — award-winning vendors, with sessions and break out groups focusing on digital strategies, digital transformation, innovation management, hybrid systems and ambitious digital experiences, showcasing large-scale implementations of Drupal platforms and solutions integrating Drupal for global corporations.

Join us on September 10–14, 2018 in Darmstadt, Germany to learn first hand how Drupal enables digital transformation. You can register for the event at https://drupaleurope.org/tickets.

Present your vision at Drupal Europe

Drupal Europe is organized for the community by the community. This means everyone is invited to participate in the program and share their ideas with us. We are currently looking for submissions for sessions, panels, and workshops. To create an excellent submission, you should write a good abstract that helps track chairs and conference visitors to understand how and why you approach your topic, what will be the benefits and learnings gained by attending your session, and what is the expected experience level of the audience.

Main topics we are looking for:

  • Digital transformation with Drupal (case studies)
    What was your process of digital transformation, what were the business goals, what part Drupal plays in the solution and how did you measure success?
  • Enterprise products made for or made with Drupal

What can enterprise use to complement Drupal to support their requirements? Are there reusable solutions out there that can serve as enterprise platform?

  • Technical solutions provided with Drupal
    Having Drupal as the chosen technology for digitalization, what does Drupal offer out of the box or what did your organization develop on top of the framework?

You will speak in front of digital leaders like CTOs, CIOs and CMOs of businesses who will be there to evaluate Drupal on a strategic level. Sessions will attract people looking to gain tactical advice on how to tackle the challenges of digitalization of their organizations or their clients.

We are looking to provide value to our track’s attendees, to empower them with insights and give them information that will enable them to make better decisions when choosing Drupal as their platform of choice.

We are looking forward to great content submitted, please go to https://drupaleurope.org/speakers and propose a session at Drupal Europe before 30 June 2018.

Gegen Netflix und Amazon: ProSiebenSat.1 und Discovery mit eigenem Video-Dienst

heise online Newsticker - 27. Juni 2018 - 9:00
Die zwei Sender planen eine gemeinsame Video-on-Demand-Plattform – und laden weitere Sender wie ARD, ZDF und RTL ein, sich daran zu beteiligen.

DSGVO und Fotografie: OLG Köln schafft etwas Klarheit

heise online Newsticker - 27. Juni 2018 - 8:00
Das Kunsturhebergesetz findet laut OLG Köln auch nach Wirksamwerden der DSGVO Anwendung. Für die Bildberichterstattung bedeutet dies etwas Rechtssicherheit.

"Offensichtliches Plagiat": Bethesda verklagt Warner wegen Westworld-Mobilspiel

heise online Newsticker - 27. Juni 2018 - 8:00
Ein neues Westworld-Mobilspiel von Warner soll Fallout Shelter nicht nur nachahmen, es soll sogar auf demselben Code basieren, klagt Bethesda.

Offene Firebase-Datenbanken: Tausende Apps leaken Passwörter, Nutzerdaten etc.

heise online Newsticker - 27. Juni 2018 - 7:00
Dritte könnten mit vergleichsweise wenig Aufwand private Daten von Millionen App-Nutzern einsehen, warnen Sicherheitsforscher.

iX-Cloud-Konferenz 2018: Programm steht, Anmeldung gestartet

heise online Newsticker - 27. Juni 2018 - 7:00
Die Konferenz widmet sich der effizienten Cloud-Nutzung. Das Programm bietet ein breites Themenspektrum von DSGVO über Kubernetes bis zu Zertifizierungen.

iOS: Verwirrung um Brute-Force-Hack der Gerätesperre

heise online Newsticker - 27. Juni 2018 - 7:00
Ein Sicherheitsforscher behauptet, einen Trick gefunden zu haben, mit dem sich iPhone und iPad knacken lassen. Apple widerspricht dem.

Google Knowledge Graph: Personen und Firmen können Änderungen vorschlagen

heise online Newsticker - 27. Juni 2018 - 6:30
Der Knowledge Graph liefert Informationen bereits in den Google-Suchergebnissen. Personen und Firmen können die Einträge ändern – allerdings nicht beliebig.

Dries Buytaert: Working together to promote Drupal

Planet Drupal - 27. Juni 2018 - 0:28

The Drupal community has done an amazing job organizing thousands of developers around the world. We've built collaboration tools and engineering processes to streamline how our community of developers work together to collectively build Drupal.

This collaboration has led to amazing results. Today, more than 1 in 40 of the top one million websites use Drupal. It's inspiring to see how many organizations depend on Drupal to deliver their missions. What is equally incredible is that historically, we haven't collaborated around the marketing of Drupal. Different organizations have marketed Drupal in their own way.

In my DrupalCon Nashville keynote, I shared that it's time to make a serious and focused effort to amplify Drupal success stories in the marketplace. Imagine what could happen if we enabled hundreds of marketers to collaborate on the promotion of Drupal, much like we have enabled thousands of developers to collaborate on the development of Drupal.

Accelerating Drupal adoption with business decision makers

To focus Drupal's marketing efforts, we launched the Promote Drupal Initiative. The goal of the Promote Drupal Initiative is to do what we do best: to work together to collectively grow Drupal. In this case, we want to collaborate to raise awareness with business and non-technical decision makers. We need to hone Drupal's strategic messaging, amplify success stories and public relation resources in the marketplace, provide agencies and community groups with sales and marketing tools, and improve the Drupal.org evaluator experience.

To make Promote Drupal sustainable, Rebecca Pilcher, Director of MarComm at the Drupal Association, will be leading the initiative. Rebecca will oversee volunteers with marketing and business skills that can help move these efforts forward.

Promote Drupal Fund: 75% to goal

At DrupalCon Nashville, we set a goal of fundraising $100,000 to support the Promote Drupal Initiative. These funds will help to secure staffing to backfill Rebecca's previous work (someone has to market DrupalCon!), produce critical marketing resources, and sponsor marketing sprints. The faster we reach this goal, the faster we can get to work.

I'm excited to announce that we have already reached 75% of our goal, thanks to many generous organizations and individuals around the world. I wanted to extend a big thank you to the following companies for contributing $1,000 or more to the Promote Drupal Initiative:

If you can, please help us reach our total goal of $100,000! By raising a final $25,000, we can build a program that will introduce Drupal to an emerging audience of business decision makers. Together, we can make a big impact on Drupal.

Joachim's blog: Making builder code look like output code

Planet Drupal - 26. Juni 2018 - 23:30

One of the big challenges with updating Drupal Code Builder for Drupal 8 has been the sheer variety of code to be output. On earlier versions of Drupal, it was just about hooks, and all that needed to be done was to take the API documentation code and replace 'hook_' with the module name. There were info files too, and Drupal 7 added the placing of hooks into different .inc files, but compared to this, Drupal 8 has things like plugin annotations, fluent method calls for content entity baseFieldDefinitions(), FormAPI arrays, not to mention PHP class methods, and more.

But one of the things I enjoy about working on DCB is that I am free to experiment with different ideas, much more so than with work on core or even contrib. It is its own system, without any need to work with what a framework supplies, and it has no need to be extensible. So I can try a new way of doing things as often as I want, and clean up when I've had time to figure out which way works best.

For example, up until recently, the code for a field definition in baseFieldDefinitions() was getting generated in three different ways.

First, the old-fashioned way of doing it line by line, then concatenating the array with a "\n" to make the final code. This is the way most of the old code in DCB was done, but with things that need handling of terminal commas or semicolons, and nesting indents and so on, it was starting to get really clunky.

So then I tried writing something loosely inspired by Drupal's RenderAPI. Because that's a nice big hammer that seems to fit a lot of nails: make a big array of data, chuck your stuff into it, then hand it over to something that makes the output. Except, not so good. Writing the code to make the right sort of array was fiddly. The array of data needed to combine actual data and metadata (such as the class of an annotation), which added levels to the nesting.

Then I hit on an idea: baseFieldDefinitions() fields are a fluent interface, like this:

$fields['changed'] = BaseFieldDefinition::create('changed') ->setLabel(t('Changed')) ->setDescription(t('The time that the node was last edited.')) ->setRevisionable(TRUE) ->setTranslatable(TRUE);

What if the code that builds this could be the same, to the point where you could just copy-paste code from, say, the node entity class, and make a few tweaks? Creating the code in DCB would be much simpler, and having the DCB code look like the output code would make debugging easier too.

Using a class with the magic __call() method lets us have just that: a renderer object that treats a method call as some information about code to render. Here's what the builder code for the base field definition code looks like now:

$changed_field_calls = new FluentMethodCall; $changed_field_calls ->setLabel(FluentMethodCall::t('Changed')) ->setDescription(FluentMethodCall::t('The time that the entity was last edited.')); if ($use_revisionable) { $changed_field_calls->setRevisionable(TRUE); } if ($use_translatable) { $changed_field_calls->setTranslatable(TRUE); } $method_body = array_merge($method_body, $changed_field_calls->getCodeLines());

It's not yet perfect, as the first line isn't done by this, and the handling of the t() calls could do with some polish; probably by creating a separate class called something like FunctionCall, such that FunctionCall::somefunction() returns the code for a call to somefunction().

But the efficiency and elegance of this approach has led me to devise a new principle for DCB: builder code should look as much as possible like that code that it outputs.

So applying this approach to outputting annotations, the code now looks like this:

$annotation = ClassAnnotation::ContentEntityType([ 'id' => 'cat', 'label' => ClassAnnotation::Translation("Cat"), 'label_count' => ClassAnnotation::PluralTranslation([ 'singular' => "@count content item", 'plural' => "@count content items", ]), ]); $annotation_lines = $annotation->render();

Magic methods used there as well, this time for static calls. The similarity to the output code isn't as good, as annotations aren't PHP code, but it's still close enough that you can copy the code you want to output, make a few simple changes, and you have the builder code.

This work has embodied another principle that I've come to follow: complexity and ugliness should be pushed down, hidden, and encapsulated. Here, the ClassAnnotation and FluentMethodCall have to do fiddly stuff like quoting string values, recurse into nested arrays. They have to handle special cases, like the last line of a fluent call has a semicolon and the last line of an annotation has no comma. All of that is hidden from the code that uses them. That can get on with doing the interesting bits.