Microsoft feeds sychronization
Author: m | 2025-04-24
Decem: Sychronized with PHPMaker 2025.7.3 Template file. Decem: Sychronized with PHPMaker 2025.7.0 Template file. Novem: Sychronized with PHPMaker 2025.6.6 Template file. Novem: - Fixed Select2 does not work properly in Modal dialog. - Sychronized with PHPMaker 2025.6.4 Template file. Novem: Decem: Sychronized with PHPMaker 2025.7.3 Template file. Decem: Sychronized with PHPMaker 2025.7.0 Template file. Novem: Sychronized with PHPMaker 2025.6.6 Template file. Novem: - Fixed Select2 does not work properly in Modal dialog. - Sychronized with PHPMaker 2025.6.4 Template file. November 17
Problem with feeds sychronization - Windows XP
With the recent release of version 2.3, Anchore Enterprise now supports scanning of Windows container images and the addition of a new feed source for identifying Windows vulnerabilities: Microsoft Security Response Center (MSRC).MSRCMicrosoft Security Response Center maintains reports of security vulnerabilities affecting Windows systems in its Security Update Guide. In addition to publishing this data publicly on its website, Microsoft provides programmatic access to retrieve security update details in the Common Vulnerability Reporting Format via its Microsoft Security Update API. In order to access the API, users must obtain an API key using their Microsoft TechNet account.Enabling the MSRC Feed Driver for Anchore EnterpriseIn order to configure the feed source for use with Anchore Enterprise, the on-premise Enterprise Feeds Service must be enabled with the obtained API key. For instructions on how to obtain an API key from Microsoft, visit Anchore Enterprise Feed Driver Configuration.Note: If you are upgrading an existing deployment via docker-compose, you will need to bring down the deployment WITHOUT deleting existing volume configurations (This can be completed by omitting the ‘-v’ flag via docker-compose). For Kubernetes deployments using Helm, the upgrade can be performed using the helm upgrade command.To enable the on-premise feeds service and configure the MSRC driver on deployments using docker-compose, edit the following section of the compose template:services: ... feeds: ... environment: ... - ANCHORE_ENTERPRISE_FEEDS_MSRC_DRIVER_ENABLED=true - ANCHORE_ENTERPRISE_FEEDS_MSRC_DRIVER_API_KEY=*For deployments using the config.yaml configuration file, update the following sections:services: ... feeds: ... drivers: msrc: enabled: true api_key: To enable the feeds service and the MSRC driver for Kubernetes deployments, update the following section of your custom values file:anchore-feeds-db: enabled: true ...anchoreEnterpriseFeeds: enabled: true ... # Enable microsoft feeds msrcDriverEnabled: true msrcApiKey: ...(For new deployments on Kubernetes using the stable/anchore-engine Helm chart, refer to the installation guide for instructions on deploying Anchore in your cluster).Verify New Feed is EnabledAfter bringing up the deployment, it may take a while for the feed sync to complete depending on whether or not this is a new deployment or existing upgrade. For details on checking the status of the feeds synchronization, refer to our enterprise docs.Once the feeds have finished synchronizing, verify the MSRC feeds is included in the list:- via Enterprise UI -- or via API -Adding Windows ImagesJust as with Linux containers, you can analyze a Windows container repository or tag by providing the image registry/repository/tag in the UI or via the API: anchore-cli image addViewing Compliance and Decem: Sychronized with PHPMaker 2025.7.3 Template file. Decem: Sychronized with PHPMaker 2025.7.0 Template file. Novem: Sychronized with PHPMaker 2025.6.6 Template file. Novem: - Fixed Select2 does not work properly in Modal dialog. - Sychronized with PHPMaker 2025.6.4 Template file. Novem: Decem: Sychronized with PHPMaker 2025.7.3 Template file. Decem: Sychronized with PHPMaker 2025.7.0 Template file. Novem: Sychronized with PHPMaker 2025.6.6 Template file. Novem: - Fixed Select2 does not work properly in Modal dialog. - Sychronized with PHPMaker 2025.6.4 Template file. November 17 I'm having some sychronization issues again. Here is what happens:On my work computer (which I use most frequently), everything seems to work fine. I have it set to automatically upload/download the synchronization file at startup/exit. The upload file is typically between 500 and 600KB when I upload.When I try running this on my home computer, the initial time I start it up it works fine. Everything I've read shows up as read. The problem happens when I upload the file from the home computer. The upload file is usually around 200-300KB. When I start it up at work, quite a few of the feed items that were previously read show up unread. I can reproduce this repeatedly. I'm fairly certain I was having this issue before upgrading to the recently released Alpha versions.I'm running both of these on XP and they are both Advanced Edition 2.2.1. Any assistance would be appreciated!Comments
With the recent release of version 2.3, Anchore Enterprise now supports scanning of Windows container images and the addition of a new feed source for identifying Windows vulnerabilities: Microsoft Security Response Center (MSRC).MSRCMicrosoft Security Response Center maintains reports of security vulnerabilities affecting Windows systems in its Security Update Guide. In addition to publishing this data publicly on its website, Microsoft provides programmatic access to retrieve security update details in the Common Vulnerability Reporting Format via its Microsoft Security Update API. In order to access the API, users must obtain an API key using their Microsoft TechNet account.Enabling the MSRC Feed Driver for Anchore EnterpriseIn order to configure the feed source for use with Anchore Enterprise, the on-premise Enterprise Feeds Service must be enabled with the obtained API key. For instructions on how to obtain an API key from Microsoft, visit Anchore Enterprise Feed Driver Configuration.Note: If you are upgrading an existing deployment via docker-compose, you will need to bring down the deployment WITHOUT deleting existing volume configurations (This can be completed by omitting the ‘-v’ flag via docker-compose). For Kubernetes deployments using Helm, the upgrade can be performed using the helm upgrade command.To enable the on-premise feeds service and configure the MSRC driver on deployments using docker-compose, edit the following section of the compose template:services: ... feeds: ... environment: ... - ANCHORE_ENTERPRISE_FEEDS_MSRC_DRIVER_ENABLED=true - ANCHORE_ENTERPRISE_FEEDS_MSRC_DRIVER_API_KEY=*For deployments using the config.yaml configuration file, update the following sections:services: ... feeds: ... drivers: msrc: enabled: true api_key: To enable the feeds service and the MSRC driver for Kubernetes deployments, update the following section of your custom values file:anchore-feeds-db: enabled: true ...anchoreEnterpriseFeeds: enabled: true ... # Enable microsoft feeds msrcDriverEnabled: true msrcApiKey: ...(For new deployments on Kubernetes using the stable/anchore-engine Helm chart, refer to the installation guide for instructions on deploying Anchore in your cluster).Verify New Feed is EnabledAfter bringing up the deployment, it may take a while for the feed sync to complete depending on whether or not this is a new deployment or existing upgrade. For details on checking the status of the feeds synchronization, refer to our enterprise docs.Once the feeds have finished synchronizing, verify the MSRC feeds is included in the list:- via Enterprise UI -- or via API -Adding Windows ImagesJust as with Linux containers, you can analyze a Windows container repository or tag by providing the image registry/repository/tag in the UI or via the API: anchore-cli image addViewing Compliance and
2025-04-01I'm having some sychronization issues again. Here is what happens:On my work computer (which I use most frequently), everything seems to work fine. I have it set to automatically upload/download the synchronization file at startup/exit. The upload file is typically between 500 and 600KB when I upload.When I try running this on my home computer, the initial time I start it up it works fine. Everything I've read shows up as read. The problem happens when I upload the file from the home computer. The upload file is usually around 200-300KB. When I start it up at work, quite a few of the feed items that were previously read show up unread. I can reproduce this repeatedly. I'm fairly certain I was having this issue before upgrading to the recently released Alpha versions.I'm running both of these on XP and they are both Advanced Edition 2.2.1. Any assistance would be appreciated!
2025-04-12Fleksy Keyboard is a keyboard for Android that combines a powerful, extensive range of features with an elegant design, making it one of the most complete keyboards that you can find on this operating system.Among the most outstanding features of Fleksy Keyboard are its useful gesture shortcuts. Just by sliding a finger across the screen of your Android, you can do many different actions, such as adding words to the dictionary, adding spaces, deleting letters or words, and undoing any previous action.Advertisement Remove ads and more with TurboThere are plenty of ways to customize Fleksy Keyboard beyond changing the color or the size of the keyboard (though you can do this too). Users can change the distribution of the keys, remove the spacebar to save space, or even make the keyboard invisible.Another very interesting feature of Fleksy Keyboard is its cloud sychronization, which allows it to learn user writer patterns to offer ever-improving recommendations.Fleksy Keyboard is an excellent keyboard for Android that should provide some stiff competition for the heavyweights in its field, like Android's own Google Keyboard or the classic Swiftkey.
2025-04-17AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\WEB\FLASHVIDEO 720P.CSP%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\SKIN.ZIP%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD EULA.RTF%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\INSTALL.LOG%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\INSTALL.SSS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\UNINSTALL.EXE%WinDir%\FONTS\CALIBRI.TTFFILES[ATTR]MODIFIED:9%LOCAL APPDATA%\MICROSOFT\FEEDS\FEEDSSTORE.FEEDSDB-MS%LOCAL APPDATA%\MICROSOFT\FEEDS\MICROSOFT FEEDS~\MICROSOFT AT HOME~.FEED-MS%LOCAL APPDATA%\MICROSOFT\FEEDS\MICROSOFT FEEDS~\MICROSOFT AT WORK~.FEED-MS%LOCAL APPDATA%\MICROSOFT\FEEDS\{5588ACFD-6436-411B-A5CE-666AE6A92D3D}~\INTERNET EXPLORER SUGGESTED SITES~.FEED-MS%LOCAL APPDATA%\MICROSOFT\FEEDS\{5588ACFD-6436-411B-A5CE-666AE6A92D3D}~\WEBSLICES~\WEB SLICE GALLERY~.FEED-MS%LOCAL APPDATA%\MICROSOFT\FEEDS CACHE\INDEX.DAT%TEMP%\CE4CF87733651BF1F44DD1E02FC1A8E8%SYSDIR%\FNTCACHE.DAT%WinDir%\TASKS\USER_FEED_SYNCHRONIZATION-{600E3BA8-8EF5-4554-94FE-DB90950D3DEB}.JOBFOLDERS ADDED:38%COMMON STARTMENU%\PROGRAMS\ELECARD%COMMON STARTMENU%\PROGRAMS\ELECARD\ELECARD AVC HD SUITE DEMO BETA%COMMON STARTMENU%\PROGRAMS\ELECARD\ELECARD AVC HD SUITE DEMO BETA\ELECARD AVC HD EDITOR%COMMON STARTMENU%\PROGRAMS\ELECARD\ELECARD AVC HD SUITE DEMO BETA\ELECARD AVC HD PLAYER%COMMON STARTMENU%\PROGRAMS\ELECARD\ELECARD AVC HD SUITE DEMO BETA\ELECARD CONVERTER STUDIO AVC HD EDITION%PROGRAM FILES COMMON%\ELECARD%PROGRAM FILES%\ELECARD%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD EDITOR%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD EDITOR\COMPONENTS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD EDITOR\LANGUAGES%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\COMPONENTS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\ENGINE%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\LANGUAGES%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\LANGUAGES\XMUXER%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\MODULE%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\SKINS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD AVC HD PLAYER\SOURCEDIALOGS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\COMPONENTS%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\LANGUAGES%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\LAYOUT%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\MEDIA%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\AVCHD%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\BLU-RAY%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\CD%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\DV%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\DVB-H%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\DVCPRO%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\DVD%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\EDITING%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\HDV%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\PORTABLE%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\STORAGE%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\STREAMING%PROGRAM FILES%\ELECARD\ELECARD AVC HD SUITE DEMO\ELECARD CONVERTER STUDIO AVC HD EDITION\PROFILES\WEB
2025-04-09Is present in the configuration.php file: $api_access_key = "abc123", enter abc123 in this field. (Used when integrating SmarterTrack with the WHMCS Addon Module.) WHMCS Username - Provide the username of an admin-level user within WHMCS who has API Access. (Used when integrating SmarterTrack with the WHMCS Addon Module.) WHMCS Password - Provide the password associated with the admin username. (Used when integrating SmarterTrack with the WHMCS Addon Module.) The following options are available from the content pane toolbar: Save - Saves the changes made to the options on the tab. Test Settings - Use this button to test your translation settings with the appropriate provider. Reset Statistics - This button will reset the character count that is tracked for character conversions using the appropriate translation service. This can be used to check against any reports received or viewed at the translation service website to ensure both systems are in sync.External FeedsExternal feeds allow users to have custom RSS feeds, and snippets of the information in articles or news items, displayed on their portal. External Feeds are different than Custom Links in that the feed snippet is displayed on the Portal home page as a section of the Portal. Custom Links create a new button on the Portal home page.If any external feeds are available, they will be listed on this page. Otherwise, new feeds can be added by clicking Add in the content pane toolbar. External feeds can be associated with all brands or used and customized on a per-brand basis. Furthermore, if multiple feeds are to be displayed on a brand's portal, they will be displayed in order of how they are listed in the Connected Services settings. Use the Move column to adjust the order of the external feeds, if needed.SmarterTrack ConnectionsAdministrators can use this section to connect to another, separate SmarterTrack installation for ticket transferring. This can be useful for those organizations working out of separate geographic locations or across sister-companies where 2 separate instances of SmarterTrack are installed. When a SmarterTrack installation is connected, agents can choose whether to transfer tickets to the local or connected instance.note: Both installations must be running the same version of SmarterTrack in order for this feature to work properly.To add a SmarterTrack instance, click Add in the content pane toolbar. A modal window will display the following options: Connection Name - The friendly name of the SmarterTrack instance. SmarterTrack Base URL - The URL for the SmarterTrack portal. Admin Username - A system administrator's username for the SmarterTrack instance. Admin Password - A system administrator's associated password for the SmarterTrack instance. OAuth Connection In the last couple of years (beginning in 2023), Microsoft has significantly changed how it allows third-party products to authenticate against services such as Microsoft 365 (Office365), Outlook.com, Hotmail, and other Exchange services. As a result, SmarterTrack has to utilize a Microsoft Azure OAuth application, maintained by SmarterTools, that allows SmarterTrack to connect to these services. This Azure OAuth application includes a 'secret key' that Microsoft requires
2025-04-15Security context constraint synchronization with pod security standardsOpenShift Container Platform includes Kubernetes pod security admission. Globally, the privileged profile is enforced, and the restricted profile is used for warnings and audits.In addition to the global pod security admission control configuration, a controller exists that applies pod security admission control warn and audit labels to namespaces according to the SCC permissions of the service accounts that are in a given namespace.Namespaces that are defined as part of the cluster payload have pod security admission synchronization disabled permanently. You can enable pod security admission synchronization on other namespaces as necessary.The controller examines ServiceAccount object permissions to use security context constraints in each namespace. Security context constraints (SCCs) are mapped to pod security profiles based on their field values; the controller uses these translated profiles. Pod security admission warn and audit labels are set to the most privileged pod security profile found in the namespace to prevent warnings and audit logging as pods are created.Namespace labeling is based on consideration of namespace-local service account privileges.Applying pods directly might use the SCC privileges of the user who runs the pod. However, user privileges are not considered during automatic labeling.Controlling pod security admission synchronizationYou can enable or disable automatic pod security admission synchronization for most namespaces.Namespaces that are defined as part of the cluster payload have pod security admission synchronization disabled permanently. These namespaces include:defaultkube-node-leasekube-systemkube-publicopenshiftAll system-created namespaces that are prefixed with openshift-, except for openshift-operatorsBy default, all namespaces that have an openshift- prefix are not synchronized. You can enable synchronization for any user-created openshift-* namespaces. You cannot enable synchronization for any system-created openshift-* namespaces, except for openshift-operators.ProcedureFor each namespace that you want to configure, set a value for the security.openshift.io/scc.podSecurityLabelSync label:To disable pod security admission label sychronization in a namespace, set the value of the security.openshift.io/scc.podSecurityLabelSync label to false.Run the following command:$ oc label namespace security.openshift.io/scc.podSecurityLabelSync=falseTo enable pod security admission label sychronization in a namespace, set the value of the security.openshift.io/scc.podSecurityLabelSync label to true.Run the following command:$ oc label namespace security.openshift.io/scc.podSecurityLabelSync=trueAbout pod security admission alertsA PodSecurityViolation alert is triggered when the Kubernetes API server reports that there is a pod denial on the audit level of the pod security admission controller. This alert persists for one day.View the Kubernetes API server audit logs to investigate alerts that were triggered. As an example, a workload is likely to fail admission if global enforcement is set to the restricted pod security level.For assistance in identifying pod security admission violation audit events, see Audit annotations in the Kubernetes documentation.Identifying pod security violationsThe PodSecurityViolation alert does not provide details on which workloads are causing pod security violations. You can identify the affected workloads by reviewing the Kubernetes API server audit logs. This procedure uses the must-gather tool to gather the audit logs and then searches for the pod-security.kubernetes.io/audit-violations annotation.PrerequisitesYou have installed jq.You have access to the cluster as a user with the cluster-admin role.ProcedureTo gather the audit logs, enter the following command:$ oc adm must-gather -- /usr/bin/gather_audit_logsTo output the
2025-03-27