ARM processor and Raspbian Support

I need a solution

Hello all, I am an IT tech for a large eneterprise and we currently use Symantec Endpoint Encryption to auto encrypt all files being transfered to a removable device. This works very well and I am glad we use it however we have run into a bit of a snafu. We have some “smart TV’s” that the administration likes to play slide shows on and we have in the past created a slideshow and saved it as a .wmv file on a USB drive and then connected it to the TV and it was able to play the video on repeat all day and administration was able to change it up whenever they wanted. Now that we are using SEE and the Removable Media Access Tool the file is encrypted and the TV that runs some version of Android cannot launch the .exe in order to decrypt the file. I suggested we use a Raspberry PI and put them behind the TV connected with HDMI. That does not seem to work either for many reasons, ARM cpu architecture,debian based OS etc… So I tried the Windows IoT for ARM build but I have not had success with this either. Has anyone else run into an issue like this before? Is there a way to run the Removable Media Access Utility from and ARM based device on a Debian OS or am I just out of luck and we will have to re evaluate security measures? 



[webapps] Joomla! Component JBuildozer 1.4.1 – ‘appid’ SQL Injection

Search for: Recent Posts. VU#144389: TLS implementations may disclose side channel information via discrepencies between valid and invalid PKCS#1 padding · Debian Security Advisory 4058-1 · Debian Security Advisory 4060-1 · macOS / iOS IOTimeSyncClockManagerUserClient Use-After-Free …


Request for Debian/s390x image in cloud


There is already a supported Debian/s390x port. Would it be possible to allow use of such an image in container? Alternatively, is it possible to use an Ubuntu container? I could then try to migrate to Debian changing the apt sources. Currently I only see the RHEL and SLES images available for selection.




Is the root account enabled during creation of Debian OVA image for IBM API Connect developer portal?

Is the root account enabled during creation of Debian OVA image for IBM API Connect developer portal?

Developer portal is built upon the Debian Linux distrubtion.
During the OS install Debian Linux will prompt the user to specifiy a root or not?
From the Debian wiki (
At installation time, you are asked whether you want to use the root account or not.
If you want to (the default), you’ll be asked to provide a complex password for root. Use a strong one!

If not, no root account is enabled and the password of the first user created will be used for administration tasks.

Question: What option was chosen during installation/creation of Debian OVA image for portal?


Package “” failed.

Product: SQL Server
Event ID: 12291
Source: SQLISPackage100
Version: 10.0
Component: Integration Services
Message: Package “” failed.

The specified Integration Services package was unable to finish running and has stopped.

Possible Causes

There are many possible causes for a package to stop running. This message might appear because of one of the following problems:

  • The data sources, files, or credentials that were specified on the development computer are not available or are not valid on the computer on which the package was deployed.

  • Data providers that were available on the development computer are not available on the computer on which the package was deployed. Or, data providers that were available in 32-bit versions are not available when the package is run as a 64-bit package.

  • The permissions that are required by the package are not sufficient when the package is scheduled in a SQL Server Agent job.

User Action

Depending on whether the error that caused the package to stop running is unexpected, you might have to take one of the following steps.

  • If the error is unexpected, review the troubleshooting suggestions for Integration Services packages. These suggestions include the use of logging and of debug dump files to learn more about what is causing the package to fail. For a list of troubleshooting suggestions, see Troubleshooting Package Execution.

  • If the error that caused the package to stop running is expected to occur occasionally, try one of the following options:

    • Consider using an error handler to handle the error. For more information, see Integration Services Event Handlers.

    • Consider using checkpoints to restart the package from a specific point. For more information, see Using Checkpoints in Packages.

    • Consider using transactions to ensure the integrity of your data. For more information, see Incorporating Transactions in Packages.