# policies Published articles for policies. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## AI Cost Visibility: Why Policies Don't Stop Surprise Bills DevFeed: [AI Cost Visibility: Why Policies Don't Stop Surprise Bills]() Original publisher: [Read original article]() Author: Kelsey Rosen Published: 2026-09-17T00:00:00Z Content type: opinion Language: en Sources: [Harness Blog]() Topics: [Artificial Intelligence](), [finops]() Tags: [ai](), [cost](), [finops](), [governance](), [organizations](), [policies](), [report](), [visibility]() ### AI overview Organizations are establishing AI spending policies but continue to receive unexpected bills because policies do not provide sufficient cost visibility or enforcement. The article argues that AI spending requires FinOps governance capable of tracking actual usage, detecting issues such as oversized models and retry loops, and assigning clear ownership. ### Source excerpt Organizations are writing AI spend policies but still getting surprise bills. Learn why governance alone fails without real policies. | Blog ## Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next DevFeed: [Policy as Code in 2026: OPA, Kyverno, Cedar and What's Next]() Original publisher: [Read original article]() Author: Abhijit Pujare Eric Minick Published: 2026-09-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [policy-as-code](), [Open Policy Agent](), [rego](), [Kyverno](), [Software Engineering](), [Kubernetes](), [JSON](), [YAML](), [AI Agent]() Tags: [ai-agent](), [compliance](), [json](), [kyverno](), [opa](), [open-policy-agent](), [policies](), [policy-as-code](), [rego](), [security](), [software-engineering](), [yaml]() ### AI overview This article surveys the 2026 Policy as Code ecosystem, comparing general-purpose Open Policy Agent and Rego with specialized approaches such as Kyverno, Cedar, and agent-oriented governance. It discusses the shift toward automated, machine-readable governance, the separation of policy from business logic, and the challenges of authoring and maintaining Rego as schemas evolve. ### Source excerpt | Blog ## Fine-Grained Admin Permissions for Organizations DevFeed: [Fine-Grained Admin Permissions for Organizations]() Original publisher: [Read original article]() Author: Vlasta Ramik Published: 2026-05-07T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [Security]() Tags: [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [permissions](), [policies](), [rest-api](), [saml](), [security](), [sso]() ### AI overview Keycloak 26.7.0 adds Fine-Grained Admin Permissions support for Organizations, allowing administrators to assign organization-level manage or view access instead of requiring realm-wide administrative control. ### Source excerpt In Keycloak 26.7.0, Fine-Grained Admin Permissions (FGAP) will support Organizations as a resource type. This means you can grant an administrator permission to manage Org A while only allowing them to view Org B -- or restrict their access to a single organization entirely. No more realm-wide all-or-nothing admin access for organizations. The Problem Before this release, administering organizations required the manage-realm role, which grants far broader access than just organizations -- it covers realm settings, authentication flows, and much more. There was no way to grant someone access to manage organizations without also giving them control over the entire realm. In multi-tenant deployments where different teams or partners own different organizations, this was a significant security and operational concern. What's New Two changes in Keycloak 26.7.0 work together to solve this: Organization-Specific Admin Roles Organizations will support scoped admin roles that let you delegate day-to-day management tasks without granting realm-wide access. An organization administrator can: Create, update, and delete organizations Invite new members and revoke membership Link and unlink identity providers Manage organization groups These roles grant access to all organizations in the realm and can only be assigned by realm administrators, ensuring that privilege escalation stays under control. Organizations as a FGAP Resource Type Organizations will be a first-class resource type in the Fine-Grained Admin Permissions system, alongside Users, Groups, or Clients. This brings two permission scopes for organizations: manage -- full administrative control over the organization view -- read-only access to the organization and its configuration When FGAP is enabled, permissions can be set per organization. An administrator who is granted manage and view on Org A and view on Org B will see both organizations, but would be able to update (or make other managerial tasks) just Org A in the ## How to Secure Microservices with SPIFFE and Istio DevFeed: [How to Secure Microservices with SPIFFE and Istio]() Original publisher: [Read original article]() Author: info@goteleport.com (Jeff Ellin, Boris Kurktchiev) Published: 2026-02-20T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [istio](), [Microservices](), [SPIFFE](), [Zero Trust](), [Authorization](), [Architecture & Design](), [Secrets Management](), [certificates]() Tags: [architecture](), [authorization](), [backend](), [certificates](), [cloud-native](), [firewalls](), [how-to](), [istio](), [kubernetes](), [microservices](), [policies](), [secrets-management](), [security](), [service-mesh](), [spiffe](), [zero-trust]() ### AI overview This guide explains how to secure microservices with SPIFFE identities, Istio service-mesh mTLS, short-lived certificates, and Zero Trust authorization policies. It addresses the limits of network-based trust and long-lived certificates in dynamic Kubernetes environments. ### Source excerpt Learn how to deploy a secure microservices application, configure default-deny authorization policies, and rebuild service connectivity with SPIFFE-based allow rules. ## Immediate, Automated, Compliant Access Enforcement with Teleport JIT Watcher DevFeed: [Immediate, Automated, Compliant Access Enforcement with Teleport JIT Watcher]() Original publisher: [Read original article]() Author: dan.johns@goteleport.com (Dan Johns) Published: 2025-08-29T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [JIT](), [Security](), [Monitoring](), [DevOps](), [API](), [Go]() Tags: [api](), [devops](), [go](), [jit](), [least-privilege](), [monitoring](), [policies](), [security]() ### AI overview This article presents a Go-based Teleport JIT Watcher that continuously enforces just-in-time access policies. It connects to Teleport's gRPC API using Machine ID, reviews access requests every 30 seconds, automatically approves compliant requests, denies policy violations, and locks old requests to limit access accumulation. ### Source excerpt Immediate, Automated, Compliant Access Enforcement with Teleport JIT Watcher A common request we hear at Teleport is for immediate Just-in-Time (JIT) access. Users shouldn't have standing access to resources, but they do need an audited escalation and approval process they can personally execute when access is required. This raises an important challenge: how do we ensure users only access the resources they truly need, without creating access sprawl or slowing teams down? ## 3 VNet Use Cases to Simplify Internal Access (Without VPNs) DevFeed: [3 VNet Use Cases to Simplify Internal Access (Without VPNs)]() Original publisher: [Read original article]() Author: jackson.pitts@goteleport.com (Jack Pitts) Published: 2025-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Network](), [Command-line interface](), [Access Control](), [migration](), [cURL](), [container]() Tags: [access-control](), [cli](), [container](), [curl](), [developer-tools](), [migration](), [permissions](), [policies](), [security](), [use-cases](), [vpn]() ### AI overview This article explains how Teleport VNet provides secure access to internal TCP applications and services without traditional VPNs or manual tunnels. It presents use cases involving internal APIs, private registries, developer tools, and custom DNS, and describes identity-based access controls and role-based permissions. ### Source excerpt Discover how to use Teleport VNet for secure internal access without VPN friction. Explore three real-world use cases: CLI access, internal APIs, and VPN migration. ## Achieving Fine-Grained Admin Permissions with Keycloak 26.2 DevFeed: [Achieving Fine-Grained Admin Permissions with Keycloak 26.2]() Original publisher: [Read original article]() Author: Vlasta Ramik Published: 2025-05-14T00:00:00Z Content type: tutorial Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [Access Control](), [audit](), [Security](), [console]() Tags: [access-control](), [admin](), [administration](), [audit](), [authorization](), [console](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [policies](), [saml](), [scopes](), [security](), [sso]() ### AI overview This article introduces Fine-Grained Admin Permissions V2 in Keycloak 26.2. It explains how FGAP V2 supports delegated administration and more granular management of users, clients, groups, and roles within a realm, with centralized permission management in the Admin Console. ### Source excerpt For years, Role-Based Access Control (RBAC) has been the cornerstone of authorization in many applications. Assigning users to roles provides a simple and effective way to manage access for common use cases. However, as applications become more complex and security requirements more demanding, RBAC alone often falls short. Keycloak is leveling up administrative access control with the release of Fine Grained Admin Permissions V2 a major step towards introducing delegated administration to Keycloak so that server administrators can assign management privileges to other users in a realm. By doing that, you should be able to reduce management costs and effort, and improve the overall efficiency and security of your deployments by authorizing access to specific resources in a realm. Why Fine-Grained Admin Permissions (FGAP) V2? In previous Keycloak versions, administrative access was largely driven by broad roles such as realm-admin or manage-users. While effective for simple setups, these roles often granted more access than necessary and lacked clarity around which actions they allowed. FGAP V2 introduces a cleaner, more deliberate permission model that enables: Granular access control over users, clients, groups, and roles Clear boundaries between operations--no more implicit permissions Easier management of the permissions and policies Better evaluation mechanism to allow authorization administrators audit the model ✨ Key Highlights 🧭 Centralized Permissions Management A new Permissions section in the Admin Console provides a single place to view and manage all fine-grained permissions for a realm. This simplifies navigation and makes it easier to design and audit your permission model. 🔍 Improved Manageability and Evaluation Permissions are now easier to discover, filter, and evaluate. You can inspect which scopes are assigned to which identities--making it more transparent and manageable to build tailored administrative roles. 🎯 Resource-Specific and Global Permissi ## Teleport 17 Adds Scalable Infrastructure Access and AWS IAM Identity Center Integration DevFeed: [Teleport 17 Adds Scalable Infrastructure Access and AWS IAM Identity Center Integration]() Original publisher: [Read original article]() Author: eddie@goteleport.com (Eddie Glenn) Published: 2025-01-14T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [Scalability](), [Security](), [IAM Identity Center](), [Resilience](), [Azure](), [Google Cloud Platform (GCP)](), [Automation]() Tags: [aws-iam-identity-center](), [azure](), [google-cloud](), [improvements](), [infrastructure](), [least-privilege](), [multi-cloud](), [permissions](), [policies](), [release](), [scalability](), [security]() ### AI overview Teleport 17 is a release focused on improving scalable, secure, and resilient infrastructure access. It adds AWS IAM Identity Center integration, supports access management across multiple AWS accounts, and introduces nested access lists with hierarchical and inherited privileges. ### Source excerpt Teleport 17 is a major release enhancing scalability, security, and resilience. Explore new features, improvements, breaking changes, and deprecations. ## Introducing Teleport 17 - Enhanced Security and Usability with New Features DevFeed: [Introducing Teleport 17 - Enhanced Security and Usability with New Features]() Original publisher: [Read original article]() Author: ben@goteleport.com (Ben Arent) Published: 2025-01-14T00:00:00Z Content type: release Language: en Sources: [Teleport]() Topics: [AWS IAM Identity Center](), [releases](), [Security](), [Amazon Web Services](), [Usability]() Tags: [aws](), [aws-iam-identity-center](), [identity](), [new-features](), [organization](), [permissions](), [policies](), [release](), [security](), [upgrade](), [usability]() ### AI overview Teleport 17 is a major release focused on scalable and secure infrastructure access. It adds preview support for AWS IAM Identity Center, including SCIM-based synchronization of users and roles, and introduces additional Teleport Identity Security features. ### Source excerpt Teleport 17 is a major release that includes AWS IAM Identity Center, new Teleport Identity Security features, and updates to Teleport Workload Identity. ## You probably shouldn't hire a Developer Advocate yet DevFeed: [You probably shouldn't hire a Developer Advocate yet]() Original publisher: [Read original article]() Author: Julien Published: 2024-11-03T17:46:31Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [developer-relations](), [Developer experience]() Tags: [advice](), [advocacy](), [community](), [company](), [developer](), [developer-experience](), [devrel](), [hiring](), [policies](), [strategy]() ### AI overview The article argues that companies should often address internal mindset, retention, career growth, compensation, and product-development practices before hiring a Developer Advocate. It also emphasizes Developer Experience as an early foundation for a healthy developer community. ### Source excerpt Many companies with job ads out for Developer Advocates don't know that's not what they should be hiring for (yet). More often than not, what they need first is some internal mindset change. And even then, a Developer Experience will go a long way to achieve the first stages of a healthy community. ## Why "Europe Must Invest" Is an Imprecise Call for European Action DevFeed: [Why "Europe Must Invest" Is an Imprecise Call for European Action]() Original publisher: [Read original article]() Published: 2024-07-09T08:51:53Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [Artificial Intelligence](), [communications](), [email]() Tags: [ai](), [communications](), [email](), [eu](), [europe](), [government](), [invest](), [meetings](), [policies](), [politics](), [reports]() ### AI overview The article argues that calls for "Europe" to invest in technology are imprecise because Europe is not a single actor and "invest" can mean either spending money or producing policies and reports. It urges writers to identify the responsible institution or group and specify the proposed action. ### Source excerpt "Be even more suspicious [...] of all those who employ the term 'we' or 'us' without your permission. This is another form of surreptitious conscription, designed to suggest that 'we' are all agreed on 'our' interests and identity. [...] Always ask who this 'we' is" - Christopher Hitchens in Letters to a Young Contrarian. It is so easy to write "Europe must invest more in AI", but it is a red flag that reveals sloppy thinking on two levels. ## Add-on Controls for Pay-As-You-Go Customers DevFeed: [Add-on Controls for Pay-As-You-Go Customers]() Original publisher: [Read original article]() Author: Vivek Viswanathan Published: 2024-04-03T23:23:00Z Content type: release Language: en Sources: [Heroku]() Topics: [Heroku](), [Security](), [Authorization](), [Single sign-on (SSO)]() Tags: [add-ons](), [announcement](), [heroku](), [heroku-enterprise](), [news](), [permissions](), [policies](), [security]() ### AI overview Heroku has extended add-on controls to Heroku Teams for Pay-As-You-Go customers. Team admins can create an allowlist and restrict non-admin members to installing only approved add-ons. Existing unapproved add-ons remain installed. ### Source excerpt Add-on Controls for Heroku Teams At Heroku, trust and security are top priorities and we've been steadily adding more security controls to the platform. Recently, we launched SSO for Heroku Teams, and today, we're excited to announce more enhancements for teams: add-on controls. Previously, this feature was only available to Heroku Enterprise customers. The Elements [...] The post Add-on Controls for Pay-As-You-Go Customers appeared first on Heroku. ## jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more DevFeed: [jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more]() Original publisher: [Read original article]() Author: lukaseder Published: 2023-12-15T16:30:41Z Content type: release Language: en Sources: [jOOQ]() Topics: [releases](), [DuckDB](), [CockroachDB](), [Maven](), [Gradle](), [rdbms](), [Multi-tenancy]() Tags: [cockroachdb](), [cockroachdb-23](), [duckdb](), [gradle](), [gradle-plugin](), [implicit-joins](), [java-8](), [join-paths](), [jooq](), [jooq-3-19](), [jooq-development](), [maven](), [maven-repository](), [multi-tenancy](), [oracle-23c](), [policies](), [release-notes](), [releases](), [row-level-security](), [security](), [trigger-meta-data](), [triggers](), [trino](), [trinodb](), [udt-paths](), [udts]() ### AI overview The jOOQ 3.19.0 release adds experimental DuckDB support, Trino support, and support for CockroachDB 23 and Oracle 23c. It also improves join paths, introduces an official Gradle plugin and a commercial Maven repository, and adds policies for row-level security. ### Source excerpt New Dialects It's been a few releases since we've added support for new dialects, but finally some very interesting RDBMS of increasing popularity have joined the jOOQ family including: These dialects are available in all jOOQ editions. New dialect versions In addition to these entirely new dialects, big new CockroachDB and Oracle versions have shipped: ... Continue reading jOOQ 3.19.0 Released with DuckDB, Trino, Oracle 23c support, join path improvements, an official gradle plugin, commercial maven repositories, policies, UDT paths, trigger meta data, hierarchies, and much more -> ## S3 Policies Explained: Bucket Policies vs IAM Policies vs ACLs DevFeed: [S3 Policies Explained: Bucket Policies vs IAM Policies vs ACLs]() Original publisher: [Read original article]() Author: ratneshmaurya2311@gmail.com (Ratnesh Maurya) Published: 2023-11-23T00:00:00Z Content type: tutorial Language: en Sources: [Ratn Labs]() Topics: [Amazon S3](), [Access Control](), [AWS IAM](), [Authorization](), [Encryption](), [JSON]() Tags: [access-control](), [aws](), [backend](), [cloud-devops](), [cloud-devops-backend](), [encryption](), [examples](), [iam](), [json](), [permissions](), [policies](), [s3]() ### AI overview A tutorial explaining how Amazon S3 access control works by comparing bucket policies, IAM policies, and ACLs, with JSON examples covering public read access, encryption enforcement, and user-scoped permissions. ### Source excerpt How S3 access control works -- bucket policies vs IAM policies vs ACLs, with JSON examples for public read, encryption enforcement, and user-scoped permissions. ## Keycloak 21.0.0 released DevFeed: [Keycloak 21.0.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2023-02-23T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [saml](), [Cordova](), [Microsoft](), [Hibernate](), [JavaScript](), [PostgreSQL]() Tags: [cordova](), [hibernate](), [idm](), [javascript](), [kerberos](), [keycloak](), [keycloak-release](), [ldap](), [microsoft](), [migration-guide](), [openid-connect](), [policies](), [postgresql](), [release](), [saml](), [sso](), [update]() ### AI overview Keycloak 21.0.0 is released with new features, enhancements, documentation updates, and resolved issues. Changes include Microsoft Authenticator support, multi-hosted-domain support for GoogleIdentityProvider, Cordova redirect URI configuration, SAML signature updates, and storage improvements. ### Source excerpt To download the release go to Keycloak downloads. Upgrading Before upgrading refer to the migration guide for a complete list of changes. All resolved issues New features #11698 Add an option allowing to disable client registration access token rotation keycloak #15271 Add support for Microsoft Authenticator keycloak #16107 Short verification_uri for Device Authorization Request keycloak #16787 support multi hosted-domain in `GoogleIdentityProvider` keycloak #17037 Allow configuring of redirectUri for the cordova adapter keycloak adapter/javascript Enhancements #1738 Deprecate SHA1 based algorithms for SAML signatures keycloak-documentation #1743 Documentation of some options of SAML IDP is not up-to-date keycloak-documentation #8820 Official Support for Microsoft mobile authenticator app keycloak #8982 Blacklist false positive rate could be set a lot lower. keycloak #9008 Update client with registration access token gained by client registration keycloak authorization-services #9017 Pre-authorization hook for client policies keycloak #9144 Remove Hashicorp Support keycloak dist/quarkus #9388 Global lock interface keycloak storage #9420 Use bulk deletes in HotRod store keycloak storage #9699 Include list of possible option values in help messages. keycloak dist/quarkus #10018 JPA Map Storage: leverage function-based indexes (Postgresql) keycloak storage #10090 Remove workaround in HotRodUtils#paginateQuery keycloak storage #10376 Add MapKeycloakTransaction.exists(id) method keycloak storage #10988 Remove doubled field from HotRod entities keycloak storage #11744 Remove `session.area().getById(id)` from Map provider methods keycloak storage #12067 Investigate a way to update indexes in no-downtime way for HotRod store keycloak storage #12068 Leverage Infinispan lifespan for ExpirableEntities in HotRod storage keycloak storage #12950 Implement "advanced claim to group" mapping for SAML keycloak #13219 Followup: JPA Map store wants to use `hibernate.integrator_provider ## Securing Cloud Infrastructure with Teleport and AWS Identity Federation DevFeed: [Securing Cloud Infrastructure with Teleport and AWS Identity Federation]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-08-25T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Amazon Web Services](), [Cloud](), [cloud-infrastructure](), [AWS IAM](), [Access Control](), [Authorization](), [DevOps](), [Amazon EC2](), [Amazon EKS](), [Amazon S3]() Tags: [access-control](), [account](), [aws](), [cli](), [cloud](), [cloud-computing](), [cloud-infrastructure](), [credentials](), [devops](), [iam](), [identity](), [infrastructure](), [integration](), [least-privilege](), [managed-services](), [operations](), [organization](), [platform](), [policies](), [security]() ### AI overview This article explains how Teleport and AWS Identity Federation can centralize access to AWS cloud infrastructure. It describes account and user sprawl, federated IAM access, least-privilege delegation, just-in-time privilege escalation, and policy enforcement across the AWS console, SDK, and CLI. ### Source excerpt The rise of cloud computing has proliferated AWS accounts and users--essential partners for enterprises tackling long-term strategic initiatives and day-to-day DevOps. ## A deep dive into Temporal's access control strategy in AWS DevFeed: [A deep dive into Temporal's access control strategy in AWS]() Original publisher: [Read original article]() Author: Brandon Sherman Published: 2022-06-06T07:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Access Control](), [Amazon Web Services](), [AWS IAM](), [Authorization](), [Cloud]() Tags: [access-control](), [aws](), [breach](), [cloud](), [deep-dive](), [iam](), [isolation](), [permissions](), [policies](), [strategy](), [temporal-concepts]() ### AI overview Temporal describes its strategy for securing its AWS cloud environment by segmenting accounts into rings to limit blast radius and strengthen isolation. The article also discusses implementing the approach with AWS service control policies and the role of IAM. ### Source excerpt This blog post gives some insight into Temporal's strategy for securing our cloud environment. It also calls attention to an unexpected facet of AWS access policies encountered along the way. ## How to Configure SSO for Amazon RDS Authentication and Authorization DevFeed: [How to Configure SSO for Amazon RDS Authentication and Authorization]() Original publisher: [Read original article]() Author: info@goteleport.com (Janakiram MSV) Published: 2022-05-13T00:00:00Z Content type: tutorial Language: en Sources: [Teleport]() Topics: [Amazon RDS](), [Single sign-on (SSO)](), [Authorization](), [okta](), [saml](), [Authentication](), [Amazon Web Services](), [PostgreSQL](), [Amazon EC2]() Tags: [amazon-rds](), [authentication](), [authorization](), [aws](), [how-to](), [okta](), [policies](), [postgresql](), [saml](), [security](), [sso](), [tutorial]() ### AI overview A tutorial explains how to configure single sign-on for Amazon RDS using Okta, SAML, and Teleport. It shows how to map Okta groups to Teleport roles and use role-based access control to restrict access to specific databases, including a sensitive forecast database. ### Source excerpt This post is a tutorial to set up single sign-on (SSO) for Amazon RDS access ## How Companies Without Racists Perpetuate Racism DevFeed: [How Companies Without Racists Perpetuate Racism]() Original publisher: [Read original article]() Author: info@goteleport.com (Kafi Payne) Published: 2020-06-09T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [systems](), [.env]() Tags: [equity](), [hiring](), [inclusion](), [organizational-culture](), [policies]() ### AI overview The article argues that companies can perpetuate racism even without explicitly racist employees or policies when they respond to racial injustice with statements but fail to address systemic racism through sustained anti-racist action. It uses Teleport's own shortcomings in diversity, equity, and inclusion as a candid example. ### Source excerpt It is not enough to not be racist. We need to actively be anti-racist. Teleport is committing to diversity - Black Lives Matter. ## Teleport Open Source Organizational Culture DevFeed: [Teleport Open Source Organizational Culture]() Original publisher: [Read original article]() Author: info@goteleport.com (Kafi Payne) Published: 2020-02-19T00:00:00Z Content type: opinion Language: en Sources: [Teleport]() Topics: [Open Source](), [Software Engineering](), [Development]() Tags: [collaboration](), [community](), [hiring](), [onboarding](), [open-source](), [organizational-culture](), [policies]() ### AI overview This opinion piece explains how Teleport applies open-source principles such as transparency, collaboration, accountability, written contributions, and shared responsibility to organizational culture, HR policies, onboarding, feedback, and hiring. ### Source excerpt This post focuses on the way that open source elements influence Teleport's organizational culture, human resources, and hiring. ## Keeping the Internet Secure DevFeed: [Keeping the Internet Secure]() Original publisher: [Read original article]() Author: Adam Published: 2018-07-17T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [Digital Security](), [Encryption](), [Cybersecurity](), [Security]() Tags: [australia](), [cybersecurity](), [digital-security](), [encryption](), [global](), [government](), [law](), [organizations](), [policies](), [security]() ### AI overview A global coalition of civil society and technology experts urged the Australian government to abandon proposed legislation that would require device manufacturers to help law enforcement access encrypted information. The letter argues that weakening encryption would threaten individual rights, economic safety, and security, while calling for collaboration on law-enforcement adaptation to the digital era. ### Source excerpt [no description provided] ## GPO: Instalacja GIMP'a 2.8 DevFeed: [GPO: Instalacja GIMP'a 2.8]() Original publisher: [Read original article]() Author: Tom Published: 2013-08-06T00:00:00Z Content type: tutorial Language: pl Sources: [Tomasz Gągor]() Topics: [Batch file](), [active directory](), [enterprise deployment](), [Script](), [Windows](), [configuration](), [App]() Tags: [active-directory](), [code](), [gpo](), [install](), [installation](), [policies](), [startup](), [windows]() ### AI overview A Polish tutorial explains how to deploy GIMP 2.8 through an Active Directory Group Policy startup script on Windows. The batch script checks whether GIMP is installed, silently removes an earlier manually installed version, and installs GIMP 2.8 from a network share. ### Source excerpt Raz na jakiś czas trzeba coś niestandardowego wrzucić do instalacji w Active Directory a że nie wszystkie aplikacje mają dostępne paczki MSI to trzeba się nieco natrudzić. Poniżej wrzucam skrypt, który instaluje GIMP'a 2.8 z domyślnego instalatora (wersja InnoSetup) przy okazji odinstalowując wcześniejsze wersje zainstalowane ręcznie. Zapisujemy poniższy kod jako np. gimp-install.cmd @echo off REM Installs GIMP cls echo ---------------------------------------------------- echo . echo . echo . Installing/Updating GIMP - Please Wait echo . echo . echo ---------------------------------------------------- REM Test if actual IF exist "%ProgramFiles%\GIMP\bin\gimp-2.8.exe" GOTO SkipInstall REM Exit the application taskkill.exe /F /FI "IMAGENAME eq gimp-2.8.exe" >nul REM Uninstall existing GIMP version, delete folder if exist "%ProgramFiles%\GIMP 2\uninst\unins000.exe" "%ProgramFiles%\GIMP 2\uninst\unins000.exe" /VERYSILENT :: Wait for 20 seconds ping -n 40 127.0.0.1 > NUL if exist "%ProgramFiles%\GIMP 2\" rd "%ProgramFiles%\GIMP 2\" /Q /S REM Install new version "\\serwerplikow.local\Instalki\GIMP\gimp-2.8.4-setup.exe" /VERYSILENT /NORESTART /DIR="%PROGRAMFILES%\GIMP 2.8" REM Skip installation if acctuall :SkipInstall REM Return exit code to SCCM exit /B %EXIT_CODE% Tworzymy nową regułkę GPO i zmierzamy do: Computer Configuration\Policies\Windows Settings\Scripts\Startup W nowym okienku wybieramy Show Files... Wklejamy plik skryptu do tego folderu i teraz możemy dodać go w tym samym oknie (Add...) - dzięki wrzuceniu skryptu w tym miejscu będzie się on automatycznie replikować na inne kontrolery. Skrypt będzie co prawda uruchamiany przy każdym starcie komputera ale pierwszy warunek będzie sprawdzać czy aplikacja jest zainstalowana więc nie spowolni to znacznie startu.