The Association of Independent Music (AIM) represents the interests of more than 800 independent music companies in the UK.

With online copyright infringement as one of the major threats, the organization also offers assistance on the anti-piracy front.

Earlier this year, AIM teamed up with anti-piracy tracking outfit MUSO to help its members remove pirated links from the web. With MUSO’s automatic takedown service, the labels can remove infringing URLs with minimal effort.

This week AIM sent out a press release showing how much has been achieved over the past four months. The results, shared by AIM’s Head of Legal & Business Affairs Gee Davy are impressive indeed.

“AIM’s partnership with MUSO began in May this year, and to see 5 million takedowns achieved already reflects the speed and efficiency with which MUSO has covered the catalogs across the independent music community,” Davy notes.

“Our members report that they are delighted with the service, which not only protects their releases from online piracy, but creates a visual dashboard to track piracy and protection activity in real time.”

While the comments suggest that pirated content was pulled offline, the reality appears to be quite different.

The press release doesn’t mention it, but, from what we can see, the five million takedown requests were (nearly) all targeted at Google. This means that no infringing content was taken down there, only search results.

Looking more closely at all the takedown requests MUSO sent to Google, on behalf of AIM, an even more disturbing picture emerges.

Google’s Transparency Report confirms that AIM sent close to five million ‘pirate’ URLs to the search engine. However, as it turns out, the vast majority of all reported URLs were not removed. And for a good reason.

Most of the links that were reported are simply not in Google’s search index. So, logically, there is nothing to remove.

Not removed

This also means that MUSO and AIM shouldn’t refer to these as removed links, or even takedown notices. These are reports of “non-existent” search results.

While Google previously noted that it accepts takedown notices for these types of URLs in some cases, which could end up on some sort of preemptive blacklist, there is more reason for concern.

Not only are most of the reported links missing from Google’s search results, they don’t always link to anything infringing on the pirate sites either.

Here’s a random sample that was taken from one of the recent takedown requests. This shows search results on a Zooqle proxy in various languages, which appears to be automated.

Takedown request

As mentioned before, these links were never indexed by Google. However, even the torrent site in question doesn’t return any infringing content, as the searches in question return no results.

No results

The above suggests that most of these takedown efforts are rather pointless. The URLs are not in Google’s index and even if they were, many would not point to infringing content.

To us, it appears that many of these notices are automatically generated by using variations of search strings on pirate sites, whether these point to actual pirated content or not. This is something we have spotted before.

This makes it easy to get to 5 million ‘takedowns’ in four months, of course, but it is rather futile.

TorrentFreak asked both AIM and MUSO for a comment yesterday. Both confirmed receipt of our inquiry, but at the time of publication, we have yet to receive a response to our questions.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


For creators of intellectual property, from movies, TV shows and software, through to the devices that allow them to be played, Digital Rights Management (DRM) is essential to control access to those products.

Proponents argue that without the digital locks of DRM, rampant copying of their content and designs would ensue, reducing revenues and threatening the very business models that bring these products to market.

On the flip side, DRM is seen as a huge hindrance by many consumers, particularly when its existence restricts, as it always does, what legitimate buyers of content and devices are able to do with their purchases.

From copying a DVD or game disc for backup purposes through to a myriad of legitimate fair-use scenarios, DRM is an ever-present mesh of digital barbed wire laid down for the sole purpose of restricting freedom.

While DRM aims to be its own protection (which can also backfire), it is also supported by legislation. Circumvention is criminalized under the Digital Millennium Copyright Act and the EU Copyright Directive, meaning those that choose to undermine it can face the wrath of the legal system.

For these reasons and many others, the Free Software Foundation’s (FSF) Defective by Design (DbD) campaign has sought to draw attention to the anti-consumer effects of DRM. From its roots back in 2006, today the FSF celebrates its 12th annual International Day Against DRM, inviting supporters to protest against digital locks while envisioning a world without DRM.

“DRM is a major problem for computer user freedom, artistic expression, free speech, and media,” says John Sullivan, executive director of the FSF.

“International Day Against DRM has allowed us to, year after year, empower people to rise up together and in one voice declare that DRM is harmful to everyone.”

The FSF and those who share their concerns over DRM believe that the addition of digital locks actually causes damage to a product. While offering no benefits to the consumer, DRM can fail catastrophically when those behind such systems are no longer able to maintain them, resulting in “massive digital book-burnings” when content is rendered inaccessible.

DRM also gives companies a reason and a route to spy on consumers and the use of their products. ‘Phoning home’ is commonplace, allowing media companies to conduct “large-scale surveillance” over people’s viewing habits.

For these reasons and many others, FSF has been fighting against DRM for more than a decade and today they’re calling on like-minded groups and individuals to support their mission to rid the world of DRM and return freedom to consumers. With that in mind, they have set a challenge for the day.

“This year’s theme is A Day Without DRM – the FSF invites people around the world to avoid DRM for the day,” FSF writes.

“DRM is lurking in many electronic devices we use, both online and offline, and you’ll find it everywhere from media files to vehicles. Its impact is echoed in the fight for the Right to Repair and the fight for the right to investigate the software in medical devices.”

Key Day Against DRM supporters

For online dwellers, going even a few hours without DRM today is likely to prove problematic, if not impossible. Users of Windows or any Apple device, for example, will find DRM baked into the system, meaning that the only option is to use DRM-free alternatives.

And if you’re thinking of enjoying your Kindle, Netflix or Spotify, DRM is part of the deal too. Even the now-infamous Kodi has joined the party, albeit in a limited way.

The main aim of the FSF however, is to raise awareness of DRM and how it negatively affects consumers.

Content with DRM is restricted by default yet by its very nature only affects legitimate purchases. Those who pirate their software, for example, are unaffected since piracy groups remove the DRM from content before release. Bizarrely, however, some pirates have even protected their work with DRM, signalling that no one is immune. There are great alternatives, however.

The International Day Against DRM campaign site can be found here. Those looking to support FSF can do so by purchasing an anti-DRM t-shirt. It was designed by Mark Lindhout, a winner in TorrentFreak’s anti-DRM competition way back in 2007.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link



The LibreELEC 9.0 Alpha cycle has continued and releases for Amlogic and Slice hardware have been added additionally to the test cycle. We official support now Khadas VIM (AML S905X) and the LePotato (AML S905X) too. There are no plans to release LibreELEC 9.0 images for NXP/iMX6 hardware as support was removed from Kodi some months ago. Support will be reinstated in a future LibreELEC release and we will update you on progress with the next-generation Kodi video pipeline (which makes that possible) soon.

Alpha releases are important to the team because we cannot test every scenario and sometimes sidestep issues without realising. The project needs a body of regular testers to go find the problems we miss. Testing will be particularly important for LibreELEC 9.0 as Kodi v18 includes substantial internal changes to VideoPlayer and introduces new retro-gaming capabilities.

TEST NOTES

Our current focus is the OS core and we are more interested in hardware and driver bugs than Kodi problems. Please report the issues you find by starting a thread in the forums or use our bug tracker. Raspberry Pi users are reminded that dtoverlay=lirc-rpi has now been deprecated. Please read the infrared remotes wiki page  before updating.

** CAUTION **

Alpha builds exist for hands-on testing not a hands-off experience. If you run Alpha builds you must be willing to report issues and engage the LibreELEC and Kodi developers in hunting bugs. If you have no idea what a debug log is or “wife acceptance factor” is critical, these builds are not for you. If you want to run Alpha builds please make a backup and store it somewhere off-box first. Your failure to make a backup is not our problem.

Updates since v8.90.004 ALPHA:

– updated to Kodi 18 Beta 2
– improved IR remotes at all Amlogic devices
– a lot more updates and fixes, have a look at the full changelog

LibreELEC 9.0 Alpha 005 (Kodi 18 Beta 2)

To update an existing installation from within the Kodi GUI select manual update in the LibreELEC settings add-on and then check for updates; select the LibreELEC 9.0 channel and then the 8.90.005 release. To create new install media please use our simple USB/SD Creator App. The following .img.gz files can also be used to create install media or update the old fashioned way:

RPi 2/3 LibreELEC-RPi2.arm-8.90.005.img.gz (info)

RPi 0/1 LibreELEC-RPi.arm-8.90.005.img.gz (info)

Generic LibreELEC-Generic.x86_64-8.90.005.img.gz (info)

Odroid_C2 LibreELEC-Odroid_C2.arm-8.90.005.img.gz (info)

KVIM LibreELEC-KVIM.arm-8.90.005.img.gz (info)

LePotato LibreELEC-LePotato.arm-8.90.005.img.gz (info)

Slice LibreELEC-Slice.arm-8.90.005.img.gz (info)

Slice3 LibreELEC-Slice3.arm-8.90.005.img.gz (info)

WeTek_Core LibreELEC-WeTek_Core.arm-8.90.005.img.gz (info)

WeTek_Hub LibreELEC-WeTek_Hub.arm-8.90.005.img.gz (info)

WeTek_Play LibreELEC-WeTek_Play.arm-8.90.005.img.gz (info)

WeTek_Play_2 LibreELEC-WeTek_Play_2.arm-8.90.005.img.gz (info)



Source link


Terrarium TV was one of the most impressive ‘pirate’ apps in recent years. Utilizing video content hosted on file-hosting platforms, it grew to become a serious competitor to apps like Showbox and Popcorn Time.

Last week, however, developer NitroXenon announced that the project would be shutting down

“It has always been a great pleasure to work on this project. However, it is time to say goodbye. I am going to shut down Terrarium TV, forever,” he wrote.

“I know this day will come eventually. I know it would be hard to let go. But it is really time for me to move on to other projects.”

As always, people wanted to know why the project was really being shut down. TorrentFreak spoke with NitroXenon who told us….very little. When questioned he refused to speak about his motivation, which of course led to speculation, some of it reasonable, some of it less so.

The big possibility, of course, is legal threats. Given that NitroXenon refused to answer, we might deduce that he’s under pressure not to speak. However, no substantial facts were available to definitively back that up so we had to take his statement at face value.

And then this weekend, out of the blue, NitroXenon scared thousands of Terrarium TV fans with a surprise announcement.

Former users of Terrarium TV, who didn’t immediately uninstall the app as NitroXenon had previously advised, suddenly started receiving notifications on their devices.

“Uninstall immediately!” one warned. “Your IP address and location are being tracked!”

“We can’t guarantee that details won’t be shared upon request,” advised another.

These kinds of notifications are not what the average user expects and of course, panic ensued. Was this some kind of scare tactic to ensure the last few people uninstalled the app or were the notifications sent out of genuine concern for users?

On Sunday, TorrentFreak was able to reach NitroXenon and ask him what on earth is going on. He had nothing reassuring to say.

“I’m just telling the truth,” he told TF. “Almost every app tracks user’s IP [addresses]. And if I must [hand] the info to authorities then I’ll do it.”

Other than this statement, NitroXenon had nothing to add. However, on behalf of people getting the scary notifications, we asked the obvious question. Why would NitroXenon retain logs after the application had been shut down and why, if he hasn’t been asked to retain them already, didn’t he simply purge them?

We received no response but if we have to analyze this situation, we’d say that something doesn’t feel right here.

Presuming for a moment that NitroXenon has come under pressure to a) shut down the app and b) not speak about the fact that he’s been threatened, that would fit the current pattern of developers who have found themselves in a similar situation over the past few months.

That being said, if IP address and location details are indeed being logged (the app had permissions for location), then why publicly warn users that is the case? The data has already been logged and deleting Terrarium now probably isn’t going to make much difference. Also, if the aim is to collect details of pirates, why sabotage that by giving out a warning while, potentially, undermining a non-disclosure agreement?

That leads us to the possibility that these are scare tactics but, put very simply, we have no proof either way. There might be a threat and there might not but we’ve never heard of a case where people who have simply streamed content (rather than uploaded) have been pursued by content companies.

There are several other possibilities too, including that NitroXenon got sick of the whole project and decided to burn the thing to the ground (unlikely, given how friendly he was in the past) or maybe he’s having his strings pulled by parties keen to send a message to movie and TV show pirates.

To our knowledge, this is an unprecedented development for ‘pirate’ applications, no matter what is going on behind the scenes. Whether users choose to uninstall the app moving forward is their prerogative but it seems unlikely that IP address evidence would prove of much use in this case, given that Terrarium never hosted the infringing content itself.

There are no guarantees, of course, so the rumors and speculation will continue, including that a hostile third-party, not content companies, have taken over both the app and NitroXenon’s Reddit account…..

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


With software development and associated skills now accessible to millions of regular citizens, applications are released and updated every few minutes of every day.

While undoubtedly useful, the vast majority are completely benign, helpfully solving problems experienced by computer users with little fanfare.

On the other hand, applications that seek to provide simplified access to copyrighted movies, TV shows and another content face an inherently uncertain future, largely due to opposition from entertainment industry groups.

In itself, this precarious position can deter many developers but for others with an interest in file-sharing (and often the freedom from worry that comes with relative youth), the challenge can prove irresistible. As a result, dozens of applications are available today, providing mainly Android and Windows users with a free alternative to Netflix and similar products.

However, being the creator of such software presents a catch-22 situation that’s almost impossible to beat and even harder to extricate oneself from.

There is a theory that none of us ever does anything completely altruistically. Donating to charity, supporting a friend in need, or providing free access to content, are all driven by the reward we get from the experience, whether that’s pride, warm satisfaction, or the inevitable recognition.

Few app developers think that their hobby project is going to make worldwide headlines but when they are really, really good, word spreads – quickly.

Software like Popcorn Time, Showbox, or more recently Terrarium TV, all started under the radar but as their popularity grew, their developers received the confirmation that most had longed for – that their skills and hard work had resulted in something great.

This reward (and the adulation that comes with it) is an intoxicating mix that few can resist. As a result, these apps and others like them go from strength to strength, with the download numbers further encouraging their creators to continue. Meanwhile, however, we know that many would prefer not to be in the limelight.

Recently there has been some controversy in the Kodi community when popular YouTubers reviewed addons that their creators would rather have kept low-key. This publicity boosts interest but at the same time increases pressure on developers who really don’t want copyright holders knocking on their door.

The only answer, of course, is not to produce these tools in the first place. Any addon or APK that does something great WILL get traction, it’s as simple as that. There is no way to stop people talking about these tools and with that comes even more publicity. And downloads. And reward, even if grudgingly received.

Before developers know it, they have a monster on their hands, and then what? Shut it down, throwing thousands of hours of work away and losing all that recognition and feelings of reward? Or carry on, knowing that the better they do, the more likely it is that copyright holders will come calling?

In most instances, developers appear to ride the wave. With great popularity comes great responsibility, and with hundreds of thousands of users now relying on them, shutting down is difficult. And for those who generate revenue from their work via advertising or affiliate schemes, the problem is even more complicated – or straightforward – depending on perspective.

In the end, there are three basic types of developers who ‘survive’ to tell the tale.

Those who back away voluntarily with perfect timing (it’s otherwise convenient for them not to develop anymore), those who are threatened or sued into doing so, and those that somehow – against all the odds – manage to keep their identities a secret from start to finish.

Achieving the latter is not impossible but it is extremely difficult, requiring much forward planning and caution. This, it appears, is the only way to have a really successful project or application that doesn’t prove to be a huge liability when the masses really get on board.

Trouble is, few people expect this level of success at the beginning, meaning they’re ill-prepared for the fallout when things get big. Erasing online history is virtually impossible so the crumbs often lead to their demise.

An unknown pirate hero, an unsuccessful or fringe project, or legal worries. Pick one.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link


The digital world has made it much easier to buy and consume entertainment.

Whether it’s a movie, music track, or book, a shiny “buy now” button is usually just a few keystrokes away.

Millions of people have now replaced their physical media collections for digital ones, often stored in the cloud. While that can be rather convenient, it comes with restrictions that are unheard of offline.

This is best illustrated by an analogy I read a few years ago in a research paper by Aaron Perzanowski and Chris Jay Hoofnagle, titled: “What We Buy When We Buy Now.”

It goes something like this:

Imagine purchasing a book on Amazon, which is promptly delivered to your home. You put it on the bookshelf so you can crack it open on a rainy day. However, when you wake up the next morning there’s an empty spot on the shelf. The book disappeared.

In an email, Amazon customer service explains that it was recalled at the behest of a copyright holder. They quietly dispatched a drone, which entered your home at night to take the book away, and issued a refund.

This may sound utterly crazy, but in the digital world, it’s a reality. A few years ago, Amazon remotely wiped several books from customers’ Kindle e-readers because of a copyright complaint.

When these Amazon customers woke up the following day they found that the books they thought they owned, which ironically included George Orwell’s “1984,” were no longer theirs. Just like that.

This issue is much broader than just Amazon of course, there are restrictions on most of the online media you can “Buy Now.” This was brought to the forefront again this week when Anders G da Silva noticed that Apple had removed three movies from his iTunes library. Movies he bought.

Apple informed him that the movies were not accessible to “redownload” because they were no longer offered by the Canadian iTunes Store. Apparently, Apple’s license to distribute the titles has expired.

Hey Apple

In this case, it only applies to the copies that were stored in the cloud. Any movies already downloaded on a device should work fine. While not widely known, this is covered by Apple’s terms of service.

“Content may not be available for Redownload if that Content is no longer offered on our Services,” iTunes’ terms read.

Technically it makes sense. If Apple no longer has a license, they can’t distribute the files. But wouldn’t it make more sense to adapt these licensing agreements to the modern time? Why not allow indefinite redistribution to people who previously bought something legally?

Today’s reality is that ‘owning’ something in the digital world is something entirely different than owning something offline. A movie studio or book publisher can’t barge into your house and take a Blu-ray or book, but online it’s an option.

It is rare that downloaded media actually disappears from people’s devices, as happened in the aforementioned Amazon case, but there are other ‘digital’ restrictions too.

If you buy a Blu-ray disc of the latest “Pirates of the Caribbean” movie you are free to lend it to a friend, or even sell it on eBay after you’ve watched it. In the digital world that’s often not an option. You don’t really own what you buy.

This brings us back to the research paper I mentioned earlier, which was previously featured by the LA Times.

The researchers examined how the absence of the right to resell and lend affects people’s choice to buy. They found that, among those who are familiar with BitTorrent, roughly a third would prefer The Pirate Bay over Apple or Amazon if they are faced with these limitations.

These rights restrictions apparently breed pirates.

“Based on our survey data, consumers are more likely to opt out of lawful markets for copyrighted works and download illegally if there is no lawful way to obtain the rights to lend, resell, and use those copies on their device of choice,” the researchers concluded.

The paper in question is two years old by now, but still very relevant today. While we don’t expect that anything will change soon, people should at least be aware that you don’t always own what you buy.

It’s an illusion.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link

Your IP address and location are being tracked

No rest for the wicked, Terrarium TV developer NitroXenon seems to still have access into the notification system of the new modded apk of Terrarium. While most of the users are still celebrating about the modded working version of the Terrarium TV since the official Terrarium TV has shutdown, a couple new notifications that appeared on most still installed apps spread fear over users. The first notification came out yesterday with the following message as many users reported. The notification has the message: “Terrarium TV – Uninstall immediately! Your IP address and location are being tracked!”.

Terrarium TV Your IP address and location are being tracked

To be followed with a second wave of notifications that now report that they cannot guarantee your privacy: “Terrarium TV – We can’t guarantee that… details won’t be shared upon request”.

We can't guarantee that... details won't be shared upon request


While other notifications may appear in the next hours / days, it is more than clear that the developer does not want you to keep using the app. While it is also true that -hypothetically- your info can be tracked and by the way it is being tracked on any apk, website you use since everything on internet nowadays is being tracked by more than one source, if you keep using the app make sure to use a trusted and secure VPN. This is not some sort of promotion for the specific app, the common sense is to always use a VPN when connected to the internet. Not only for this apk, not only for streaming but for any transaction and interaction you do online.

I personally use IPVanish the past 3 years and I feel more than confident to recommend it to any of the people that follow me. If you do not have already a VPN and you wish to follow my advice, use the following link that will give you also a nice discount on your purchase: https://dimitrology.com/recommends/ipvanish/

 

The developer NitroXenon seems also to have appeared on Reddit where he left the following comment suggesting that is only a friendly advice and afterwards also adding that if you still use it, use it with a VPN.

Terrarium TV uninstall NitroXenon

While I personally cannot force anyone to do anything at all since everyone is free to do whatever he wants to do, I would take his advice. And always remember to use a VPN. You can never be sure on what info you share online.


After complaining that Russian Internet giant Yandex had failed to keep pirated versions of their content out of its search results, several major broadcasters filed a lawsuit with the Moscow City Court.

Gazprom-Media outlets including TNT, TV-3, 2×2, and Super went straight for the jugular, petitioning the Court to have ISPs block Yandex’s video indexing platform. The Court granted the request and gave Yandex until August 30 to remove all of the offending content.

Initially, Yandex flat-out refused. The company said the law was being misinterpreted, claiming that current legislation states that pirate content must be removed from sites hosting it and that search engine links are not covered.

However, after announcing that it would appeal the decision of the Moscow City Court, Yandex suddenly changed its mind on removing the content. Fearing its entire platform would be blocked by ISPs, Yandex erred on the side of caution, deleting all content that may (or indeed may not) have infringed the media companies’ rights.

Early September the TV channels again filed lawsuits with the Moscow City Court, again over the appearance of links to their content appearing in search results.

“Four lawsuits were filed by Yandex. In all the lawsuits, the TV channels ask the Court to oblige the defendant to stop creating technical conditions that ensure the placement of works on the Yandex.ru website,” press secretary of the court Ulyana Solopova told Interfax.

With a decision on the matter pending (and the underlying aim of Gazprom Media to reach a settlement agreement with Yandex), soon after the Moscow City Court responded to Yandex’s original appeal against a preliminary blocking injunction.

In a blow to Yandex, the Court upheld its original ruling, meaning that the decision to remove the content before an ISP ban was put in place was well-timed by the search company.

However, it now appears that the confusion over the requirements of the law will see the government step in to offer a solution. According to Russian Deputy Prime Minister Maxim Akimov, the country’s anti-piracy legislation needs to be “improved” following the Yandex/Gazprom Media dispute.

“Regarding the regulation of data in terms of copyright and intellectual property rights, of course, the improvement of legislation, including anti-piracy, is exactly necessary,” Akimov told Interfax.

“By the end of the year we will try to present the necessary amendments to the Duma, which will allow us to more clearly define the rights of the parties,” he said.

Akimov said that the amendments will be the product of negotiations between the Federal Antimonopoly Service, intellectual property bodies, and the Ministry of Economic Development and Business.

It is currently unclear which direction the talks will go and whether any changes will favor Yandex’s perception of the law or the Moscow City Court’s interpretation.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link



Team LibreELEC has been rather quiet on development and priorities for a while. Silent does not mean inactive though, so here’s an update on what’s been happening and what’s coming soon:

GBM/V4L2 and DRMPRIME

Our work on Kodi’s next-generation Linux video rendering and DRMPRIME decoding pipeline continues to make solid progress and there has been some great multi-vendor and multi-project teamwork. Initial support for the DRMPRIME decoder is part of Kodi v18 (existing in parallel with older proprietary code-paths) and we now have functional “proof of concept” LibreELEC images for the following platforms:

  • Allwinner (A20, A33, H3, H5) on Linux 4.18+
  • AMD (radeon) using VAAPI on Linux 4.18+
  • Amlogic (GXBB/GXL) on Linux 4.18+
  • Intel (i915) using VAAPI on Linux 4.18+
  • NXP (iMX6) using etnaviv on Linux 4.18+
  • Qualcomm (DragonBoard 410c) using freedreno on Linux 4.18+
  • Raspberry Pi (VC4) on Linux 4.18+
  • Rockchip (3288, 3328, 3399) using rkmpp on Rockchip Linux 4.4

Kodi is one of the first major-name apps to adopt GBM/V4L2 as a framework covering multiple GPU/SoC types so this work is elevating our project profile within the Linux community. Progress is good, but also slow as we are constantly breaking new ground, and each new improvement to Kodi and FFmpeg needs to be tested over an increasing number of GPU/SoC hardware targets which have their own individual quirks. Each platform is at a different stage of evolution, but the overall trend is that we are starting to shift focus away from code creation to code stabilisation and fixing.

There are two objectives for the next-generation pipeline; maintenance and performance. Removing older and proprietary code-paths in Kodi simplifies code and makes it easier to maintain and introduce new features that work consistently over devices that share the common GBM/DRMPRIME code path. Moving to modern code frameworks like V4L2 that use zero-copy techniques allows better performance on all hardware, but this will be most beneficial to the increasing number of low-power ARM devices that need to more efficiently process ever-increasing amounts of video data.

LibreELEC 10.0 will remove support for Xorg/X11 windowing and Nvidia (due removal at Kodi) on x86_64 hardware and move the entire distro to a common DRM/GBM video framework. In the time between now and 10.0 the team will be working to achieve feature parity so nobody notices the switch 🙂

ROCKCHIP

Forward progress on Rockchip stalled in recent months because we had to stop and adapt a large chunk of the work completed on the Rockchip Linux 4.4 kernel codebase so it could start the parallel and lengthy process of being upstreamed into the mainline kernel. This burned lots of time, but work to get the Rockchip 4.4 kernel into a reasonable state (not perfect, but usable) has now resumed. Recent commits have added initial support for HDR on RK3328/3399 devices so it’s no surprise that active-install stats have started to show an increase in the number of users running test images. RK3399 support still needs work and we also need to start thinking about the install/first-run experience. It is likely that Alpha releases for Rockchip hardware run for some time, with full release targeting LibreELEC 9.2.

ALLWINNER

Video driver development essential for LibreELEC to support newer Allwinner SoC’s is also starting to drop into place. Community developer Paul Cooper (codekipper) has started to nudge the sunxi i2s audio driver towards multi-channel audio support, and Paul Kocialkowski from the Bootlin team working on player support for their current kickstarter project joined our Slack team to contribute to our V4L2 ‘group therapy’ sessions and further the cause of the bootlin driver and Kodi support (see the Bootlin blog for demo videos).

To showcase their work on the DRM driver the bootlin team have shared an LE image. At the current time their codebase is a little behind our master branch and further behind current Kodi master branch. The majority of their code has been actively developed in collaboration with our developers working on other SoC platforms, but we need to adapt their concepts in a couple of areas so approaches remain unified over multiple SoC/GPU types. We are also waiting on mali GBM libraries to be released for the H6 chip, and we haven’t done any serious work on distro packaging. Most SoCs have hardware support challenges when bumping to mainline kernels (device trees, drivers, etc.) and we expect Allwinner hardware to be no exception. So we are still some way from making firm plans. Overall platform support needs to progress further before we can start thinking about distro packaging and initial target devices.

NXP (iMX6)

Support for the proprietary iMX6 code-path used in LibreELEC 7.x/8.x releases was dropped from Kodi v18 due to a long-term lack of maintainers and it being completely broken for 6+ months due to other code changes. Our long-term plan is to switch iMX6 releases to the new Kodi pipeline and open source ‘etnaviv’ video driver. At the current time distro packaging is mostly complete and Kodi boots and runs but video rendering for GC2000 (i.MX6q and similar) devices has some limitations that mean we cannot achieve full frame rate when rendering a 1080p video while GC3000 devices (i.MX6qp and similar) render at full speed. We will most likely wait until LE10 before we releasing images for iMX6 devices again.

AMLOGIC

Maxime Jourdan (now working for Baylibre) has made great progress on a V4L2 video decoding driver and his initial patch-set has been submitted to the kernel for review. We now have functional images for GXBB (S905) and GXL (S905X/D/W) devices running a mainline 4.18+ kernel that hardware decode the 1080p video formats we need to support. At the current time deinterlaced media is handled in software which is okay (it works) but further development will be needed to support the hardware deinterlace IP capabilities. HDMI audio is working with 2.0 output and collaboration among developers working across Amlogic, Allwinner and Rockchip (which all use the same DesignWare audio IP) is starting to fill gaps in multi-channel support. The main block to public test releases is now the DRM (Direct Rendering Manager) display driver which provides HDMI support and the foundation for DRMPRIME in Kodi. Neil Armstrong from the Baylibre team has historically worked on the DRM driver pro-bono in his spare time, but with a busy work schedule progress has been slow. LibreComputer who manufacture the popular “LePotato” board (aka, AML-S905X-CC) have agreed to fund further work under their support contract with Baylibre so Neil can schedule time and move the driver forwards. The short-term goal is HDMI 1.4 support (up to 4K/30) with a separate block of work for HDMI 2.0 following once more of the kernel framework for HDR and colourspace handling (ongoing work from Intel and AMD) is in-place. This is awesome and we’d like to publicly thank LibreComputer for their open-source commitment (Da hero’s of the hour!).

Switching Amlogic GXBB/GXL hardware to use DRMPRIME on a mainline kernel was our original stretch “Plan A” for LibreELEC 9.0 but the timescales do not align. We also considered “Plan B” with a simple delay to Amlogic releases while others moved forwards, but in the end the only sensible option was “Plan Z” and we’ve dusted off the 3.14 kernel codebase for one final round. Our goal for LibreELEC 9.0 is simply to improve on LibreELEC 8.2 by absorbing some of the less objectionable bits from community releases while expanding official support to the LePotato and Khadas VIM(1) devices. At the same time we’re not aiming for perfection, because it’s a dead and deeply flawed codebase. There is a lot more to discuss on our mainline kernel plans, but we’ll save that for a dedicated blog post after LibreELEC 9.0 has shipped.

GENERIC AND RASPBERRY PI

The team are currently working through changes to move Raspberry Pi images to Linux 4.18  (the Generic image has already bumped). Our original plan was Linux 4.14 everywhere due to it’s LTS status and use with Raspbian which would benefit Pi support, but the latest generations of Intel and AMD hardware need something newer. It also became clear the Raspberry Pi Foundation and LibreELEC are mutually interdependent. We depend on Pi Foundation staff supporting and fixing issues in the latest kernels, and the Pi Foundation depends on LibreELEC needing (and proving) the latest kernels to justify supporting them. If we remained on Linux 4.14 we removed their justification and in the long-term both sides would become stuck on a ‘safe’ kernel. Generic and Raspberry Pi releases represent 85% of our active userbase so kernel choice is an important decision and it’s taken a few rounds of passionate debate to reach agreement. Helped by a clear “don’t worry folks, we have your backs!” commitment from the Pi Foundation staff, we finally reached consensus to keep moving our kernel baseline onwards and upwards.

ALPHA, BETA and KODI

LibreELEC 9.0 Alpha releases are now running and will continue for a while as our definition of Beta is “finished product with only minor bugs” so we need to have kernel bumps etc. complete before we can progress. In the past we’ve been in lock-step with the Kodi schedule and were able to go full-release within 24 hours of Kodi 17.0, but this time around the pre-Alpha stage of development has been chaotic and we’re behind on where we’d normally expect to be in our release plan. It’s likely that Kodi 18.0 will ship before we’re done with Beta testing, but the team are working hard to move things forwards.

Thanks for reading! 🙂



Source link


Last month it was reported that a Netherlands-based repository, which contained several popular Kodi addons, had been shut down by anti-piracy group BREIN.

The Dutch developer and administrator of XvBMC-NL was visited by bailiffs in July and soon after the repository shut down. BREIN offered to settle the matter for 2,500 euros as long as the admin known as ‘Z’ signed an abstention agreement.

Months earlier, however, the XvBMC-NL repo was an unwitting participant in a campaign to infect Kodi users with cryptocurrency-mining malware, security firm ESET reports.

“According to our research, the malware we found in the XvBMC repository was first added to the popular third-party add-on repositories Bubbles and Gaia (a fork of Bubbles), in December 2017 and January 2018, respectively,” ESET writes.

“From these two sources, and through update routines of unsuspecting owners of other third-party add-on repositories and ready-made Kodi builds, the malware spread further across the Kodi ecosystem.”

ESET reports that the malware has a multi-stage architecture and uses techniques to hide the fact that the cryptominer came from a malicious addon. The miner, which is Monero-based, runs on Windows and Linux only, a relief to Android and macOS users who appear to be unaffected.

The three potential infection routes appear to be fairly cunning, ESET notes.

1. [Users] add the URL of a malicious repository to their Kodi installation so as to download some add-ons. The malicious add-on is then installed whenever they update their Kodi add-ons.

2. [Users] install a ready-made Kodi build that includes the URL of a malicious repository. The malicious add-on is then installed whenever they update their Kodi add-ons.

3. [Users] install a ready-made Kodi build that contains a malicious add-on but no link to a repository for updates. They are initially compromised, though receive no further updates to the malicious add-on. However, if the cryptominer is installed, it will persist and receive updates.

Further analysis by ESET shows that the top five countries affected by the threat are the United States, Israel, Greece, the United Kingdom and the Netherlands.

With the Bubbles repo now down, that is no longer a source for the malware. Gaia, ESET reports, is no longer serving the malicious code either. However, Kodi users who were infected could still have the malware on their machines and there’s a risk that other repos and Kodi builds could be distributing the code, “most likely” without their knowledge.

Timeline of the attack, as per ESET

A very detailed technical analysis of the attack has been published by ESET along with instructions on how users can discover if they’re affected.

“To check if your device has been compromised, scan it with a reliable anti-malware solution. ESET products detect and block these threats as Win64/CoinMiner.II and Win64/CoinMiner.MK on Windows and Linux/CoinMiner.BC, Linux/CoinMiner.BJ, Linux/CoinMiner.BK, and Linux/CoinMiner.CU on Linux,” the company reports.

“On Windows you can use the ESET Free Online Scanner, and on Linux the free trial of ESET NOD32 Antivirus for Linux Desktop, to check your computer for the presence of these threats and remove anything that is detected. Existing ESET customers are protected automatically.”

While the attack is undoubtedly serious, at the time of writing its reach appears to be limited. By examing the malware authors’ Monero wallet, ESET estimates that a minimum of 4,774 users are infected. Between them they have unwittingly generated around 5,700 euros or $6,700 for the attackers.

As ESET notes, Kodi malware is very rare. Aside from the case detailed above and the DDoS attack carried out briefly by an addon and reported here on TF, no other evidence of malware being distributed via Kodi addons has been reported.

Source: TF, for the latest info on copyright, file-sharing, torrent sites and more. We also have VPN reviews, discounts, offers and coupons.





Source link