Jump to content

Search the Community

Showing results for tags 'dsm7.0'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • General
    • Announcements
    • Emby Premiere Purchase/Subscription Support
    • Feature Requests
    • Tutorials and Guides
  • Emby Server
    • General/Windows
    • Android Server
    • Asustor
    • FreeBSD
    • Linux
    • NetGear ReadyNAS
    • MacOS
    • QNAP
    • Synology
    • TerraMaster NAS
    • Thecus
    • Western Digital
    • DLNA
    • Live TV
  • Emby Apps
    • Amazon Alexa
    • Android Mobile
    • Android TV / Fire TV
    • Emby Theater
    • iOS
    • Apple TV
    • Kodi
    • Raspberry Pi
    • Roku
    • Samsung Smart TV
    • Sony PlayStation
    • LG Smart TV
    • Web App
    • Windows Media Center
    • Plugins
  • Language-specific support
    • Arabic
    • Dutch
    • French
    • German
    • Italian
    • Portuguese
    • Russian
    • Spanish
    • Swedish
  • Community Contributions
    • Ember for Emby
    • Fan Art & Videos
    • Tools and Utilities
    • Web App CSS
  • Other
    • General Discussion
    • Developer API
    • Hardware
    • Media Clubs
    • Legacy Support

Blogs

  • Emby Blog

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 1 result

  1. eliteharbinger

    Synology DSM7.0 Beta & emby

    Hi, On one of my Synology NAS am trialling the DSM7.0 beta, however it appears that emby is not compatible. When trying to perform a repair this fails and when trying to reinstall I get the message it cant be installed due to new restrictions on installation. Synology say : https://help.synology.com/developer-guide/privilege/preface.html Lower Privilege To reduce security risks, we now provide a framework to run packages with a lower privileged "package user" instead of root. Below is a summary of how to join the framework and what package center does for you: Package developers provide privilege specification to specify what privilege is needed during program execution. During package installation, package center creates corresponding user and group. See Package User & Group for more detail. According to the privilege specification, package center chown files under /var/packages/${package}/target. (The setuid and setgid bit will be cleared) Package executables are run with privilege (package user, system or root) according to its file owner and group. See Mechanism for more detail. With this framework, package developer is capable of: Configure which executable should be run with what privilege with a simple privilege specification file. Resource Acquistion can be used to help maintain some chores that requires root privilege. Whether to lower the package's privilege and create corresponding user / group is optional. The package has to provide privilege specification to join this framework, otherwise the package will still be run with root privilege, and no user / group will be created. Is this something emby are looking at?
×
×
  • Create New...