Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Thursday May 11 2017, @12:36PM   Printer-friendly
from the what-security-issue? dept.

Microsoft's only choice to move forward is to throw the Win32 baby out with the bathwater. And that brings us to the introduction of Windows 10 S.

Windows 10 S is just like the Windows 10 you use now, but the main difference is it can only run apps that have been whitelisted to run in the Windows Store. That means, by and large, existing Win32-based stuff cannot run in Windows 10 S for security reasons.

To bridge the app gap, Microsoft is allowing certain kinds of desktop apps to be "packaged" for use in the Windows Store through a tooling process known as Desktop Bridge or Project Centennial.

The good news is that with Project Centennial, many Desktop Win32 apps can be re-purposed and packaged to take advantage of Windows 10's improved security. However, there are apps that will inevitably be left behind because they violate the sandboxing rules that are needed to make the technology work in a secure fashion.

"A casualty of those sandboxing rules is Google's Chrome browser. For security reasons, Microsoft is not permitting desktop browsers to be ported to the Store."


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Insightful) by https on Thursday May 11 2017, @06:27PM (5 children)

    by https (5248) on Thursday May 11 2017, @06:27PM (#508229) Journal

    Alternate approach that skip the intermediate step of cursing pulseaudio: go straight to BSD.

    --
    Offended and laughing about it.
    Starting Score:    1  point
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 0) by Anonymous Coward on Thursday May 11 2017, @07:37PM

    by Anonymous Coward on Thursday May 11 2017, @07:37PM (#508265)

    pulseaudio? what year is this? to think I was convinced that cursing was all about systemd nowadays?

  • (Score: 2) by stormreaver on Thursday May 11 2017, @08:05PM (3 children)

    by stormreaver (5101) on Thursday May 11 2017, @08:05PM (#508287)

    I have no idea why you're badmouthing Pulse Audio, as it has been the single best audio system ever created. Every single one of my audio problems went away with its introduction. ALSA was supposed to fix Linux audio, but its promise never materialized. It was, at best, marginally better than OSS.

    Without Pulse Audio, Linux sound management is wretchedly terrible.

    • (Score: 0) by Anonymous Coward on Thursday May 11 2017, @08:57PM

      by Anonymous Coward on Thursday May 11 2017, @08:57PM (#508321)

      To this day I still have PulseAudio problems. Every single time my desktop machine reboots, I have to go in a re-tweak the audio out settings to the correct out port (Line-out in my case, instead of the default headphone port). Yes, there's a difference and a reason not to use headphone out, but some developer somewhere seems completely ignorant of it.

      Its possible it may not be PulseAudio's issue, but the problem started when PulseAudio became the default sound system.

    • (Score: 2) by Scruffy Beard 2 on Thursday May 11 2017, @10:23PM (1 child)

      by Scruffy Beard 2 (6030) on Thursday May 11 2017, @10:23PM (#508366)

      If my audio is acting weird (noise, drop-outs), I fix it by removing pulse audio.
      To be fair, that is considered a bug [archlinux.org], but my hardware appears to support mixing though ALSA anyway.

      I have found two difficulties with this:

      • Sometimes pulseaudio does help you set up audio hardware on the fly (ie: wireless or bluetooth audio).
      • Some software, such as gnome and firefox now rely on it.
      • (Score: 1) by Scruffy Beard 2 on Thursday May 11 2017, @10:35PM

        by Scruffy Beard 2 (6030) on Thursday May 11 2017, @10:35PM (#508373)

        snd-intel-hda on some chips (seems to be fixed by " rel="url2html-28885">https://bugzilla.redhat.com/show_bug.cgi?id=485734)

        - Broken ALSA Drivers [freedesktop.org]

        But if you check the bug report, it was closed WONTFIX because the version of Fedora it was reported on reached end of support. Maybe no new comments were added because the driver was fixed in the kernel.