From b846ae79bb12bde3f07df12ae77eb7acb007948b Mon Sep 17 00:00:00 2001
From: markb74 <57717302+markb74@users.noreply.github.com>
Date: Fri, 11 Jun 2021 18:02:36 +0200
Subject: [PATCH] Allow SecurityPolicy definitions. (#8254)

Internally this was package visible to retain strict control
over the available policies. However, that kind of strict control
doesn't work with the open-source version, since users will want
to create their own policies. There's at least google-specific
policy internally.
---
 binder/src/main/java/io/grpc/binder/SecurityPolicy.java | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/binder/src/main/java/io/grpc/binder/SecurityPolicy.java b/binder/src/main/java/io/grpc/binder/SecurityPolicy.java
index 4f15e5b324..55aa33e021 100644
--- a/binder/src/main/java/io/grpc/binder/SecurityPolicy.java
+++ b/binder/src/main/java/io/grpc/binder/SecurityPolicy.java
@@ -35,11 +35,7 @@ import javax.annotation.CheckReturnValue;
 @ExperimentalApi("https://github.com/grpc/grpc-java/issues/8022")
 public abstract class SecurityPolicy {
 
-  /**
-   * Package visible constructor because we want this package to retain control over any new
-   * policies for now.
-   */
-  SecurityPolicy() {}
+  public SecurityPolicy() {}
 
   /**
    * Decides whether the given Android UID is authorized. (Validity is implementation dependent).