lorjan darleena ancher

[Darnell Rempe]

I have faced the lagging of sound problem in Youtube app as well. So far I have been watching Youtube channels. It happens from time to time when I watch HD 720p videos on Raspberry Pi 3 with remote controlling in my smartphone which Youtube supports and move the timeline/the playbar back and forth.

webOS is definitely based on Linux but I don't think it has any involvement with a distro. It's similar to how Android is based on Linux but is not called a distro. I don't have an idea about the version of Linux although that won't become a problem in most cases.

Did you try to manually install a .deb file into webOS?
I'm not exactly sure (maybe one of the devs can chip in here if I'm wrong) but I don't think you can install .deb files as in a traditional Linux distro. From what we can understand from the docs webOS only supports webapp and QML apps in the built in the .ipk package.

I mentioned this earlier, I dont think it is possible to launch traditional Linux apps on webOS. Let me repeat that; webOS is NOT Linux.
webOS is a separate operating system that shares a Linux kernel at a very low level. This does not mean traditional .deb files can be installed on webOS. That's not how it works.

Visually I think the biggest difference between webOS OSE and webOS TV is the lack of the card-based GUI that's seen on LG smart TVs.
From what I understand OSE is also optimized to work on the Raspberry Pi platform compared to the regular webOS which runs on the ARM processors in LG smart TVs. There may be many other changes under the hood, but I honestly don't know that in-depth.

I added some comments for your information.
webOS OSE is based on OpenEmbedded Yocto Linux 2.2(Morty) using raspberrypi linux kernel 4.4.y
And, Netfix app for LG webOS TV is ported on NRDP not HTML5 but Native app.
videotechnology.blogspot.com Netflix Ready Device Platform (NRDP)The Netflix Ready Device Platform (NRDP) is a software development kit used by internal and external partners to integrate Netflix into CE...

@suaji, I have one question about your Netflix demo on YouTube. Is it possible to play DRMed contents. A trailer is clean video but full video clip is DRMed stream. Can you see a full video clip ? Let us know a resolution of stream video If you possible.

Wow, that's quite interesting. I never knew that the platform developer had to port the Netflix app themselves. That's quite insightful, thank you for the clarification.
Speaking of which; by Native do you mean a QML app? I don't suppose it's Open Source and the .ipk is freely available by any chance.

webOS is a Linux system (see above), but installation of dependencies to the system is a problem. You're not going to be able to directly install a .deb or something into it, though, as you don't have the necessary package management software. As well, you're probably not going to find too many native ARM binaries for things, that play well with Wayland as a compositor. Any software that does meet those requirements, though, you should be able to build using the build system (oe), and could install it directly to the system that way.

Can we just manual install (same as in windows app portable), and open that file?.
If can, then we can set auto run startup Chromium App in linux service (systemctl)..
If succes, we can do the next step, how to Link @ Enable DRM..

We're glad you are here so we can best assist you. To use casting, the supported app must be installed on your mobile device and Roku TV. You must also connect your phone or tablet to the same wireless network as your Roku device. You can do this wirelessly with supported apps like YouTube and Netflix by opening the casting icon on the mobile device on your phone or tablet and selecting your Roku device.

I have never been able to use Android's native cast (Cast Connect) to cast through my Roku devices. Some of my previous Android phones were able to use Google Cast to cast some content (ie. Youtube, Netflix, etc-- that symbol that allowed user to cast to TV from within the opened app.)

I just use third party casting apps now when needing to cast content from my Android mobile devices to the Roku device. My personal preference is Web Video Caster (WVC), but others like Castify and Tubio work fine also.

With all the above, you install the app on your mobile device or phone (all can be found in the Play Store), and then you install a companion receiver on your Roku device. (all found in the Roku Channel Store).

The apps mentioned above are free (with ads on phone), and all offer paid features also. WVC is a one-time purchase of $3 or $4 for an ad-free full featured lifetime use, but the free version works perfectly fine. (a few additional features with the paid version).

Is there a way to cast from my mobile device to my Roku tv using Androids screen cast feature or if I'm in a mobile app for which an equivalent app is unavailable on Roku tv? I've been able to do these functions on my Android TV.

You can of course cast to your Roku TV what you are already watching on your mobile device. To use casting, the supported app must be installed on both your mobile device and your Roku streaming device. You must also make sure to connect your phone or tablet to the same wireless network as your Roku device.

You can do this wirelessly with supported apps like YouTube and Netflix by opening the casting icon on a mobile device on your phone or tablet and selecting your Roku device. The channel will launch automatically on your Roku device and playback will begin.

If you are unable to cast Netflix from your phone to your Roku TV even though you have downloaded the Netflix app on both devices and they are connected to the same Wi-Fi network, there are a few things you can try:

Note: The Screen Cast icon may be located in different locations depending on your Android phone model and version of Android. If you can't find it in the Quick Settings panel, try searching for it in the Settings app. Additionally, not all Android phones support screen casting, so make sure your device is compatible before attempting to cast.

Netflix.com, for example, sent out a notification late last week to users who made the mistake of re-using their Netflix password at Linkedin, Tumblr or MySpace. All of three of those breaches are years old, but the scope of the intrusions (more than a half billion usernames and passwords leaked in total) only became apparent recently when the credentials were posted online at various sites and services.

Netflix is taking this step because it knows from experience that cybercriminals will be using the credentials leaked from Tumblr, MySpace and LinkedIn to see if they work on a variety of third-party sites (including Netflix).

Facebook also has been known to mine data leaked in major external password breaches for any signs that users are re-using their passwords at the hacked entity. After at a breach discovered at Adobe in 2013 exposed tens of millions Adobe customer credentials, Facebook scoured the leaked Adobe password data for credential recycling among its users.

Thank you, once again, Brian, for explaining these stories in terms anyone can understand! I constantly preach to colleagues/friends/family about not re-using passwords, but I was a big offender long before my security career started.

Mik, Netflix cannot decrypt your password (nor can anyone else), as passwords are not encrypted in the first place. They are hashed. Given a password, all they can do is run it through whatever hash method they use, to see if they get matches to the hashes in their own database.

The hash returned at Netflix will amost certainly NOT be the same as the hash returned at LinkedIn, Tumblr, and others. That is because all of these places are (or should be) salting their passwords. That is, they should be adding characters to your password that they know about, but that you do not.

Even if they salt their passwords, they could check the individual passwords directly. Since what they have as input is essentially useraccount, password and what you give them when you try to log in is useraccount, password, they are essentially pretending to log in, just as you (or an attacker with the leaked credentials) and seeing if the process lets them in. If the standard login sequence accepts the password, then they need to tell you to reset it.

How do companies like Facebook and Netflix know if a password is being reused on their website(s)? Do they compare hashes? Does that mean they all use the same hashing algorithm? Is it weak security to do such?

That said, it does raise the problem of having a stolen raw pw file out there. Wait until the hackers decrypt it? Or do so first. conflicting issues there, so better public policy help (gov) would be useful.

I repeat, I think we need better public policy in this area, and yes more clear laws, rules, regulations of what is permissible and not should be put in place by government. I understand some folks do not like operating under rule of law, however that is the system we presently operate under.

When a user changes their password, they typically provide username, oldpassword, newpassword, newpassword, at that time, you could hash oldpassword twice, once to confirm the oldpassword matches the user, and once to find out which reserved password to unreserve.

The right answer to this is for browsers and password managers to default to offering to create (and store) random passwords for users for each account they create. At that point, users can stop being forced to pick passwords (we suck at picking passwords).

90f70e40cf