diff --git a/core/src/main/java/jenkins/security/CallableDirectionChecker.java b/core/src/main/java/jenkins/security/CallableDirectionChecker.java
index <HASH>..<HASH> 100644
--- a/core/src/main/java/jenkins/security/CallableDirectionChecker.java
+++ b/core/src/main/java/jenkins/security/CallableDirectionChecker.java
@@ -120,9 +120,10 @@ public class CallableDirectionChecker extends RoleChecker {
         public void onChannelBuilding(ChannelBuilder builder, Object context) {
             // if the big red emergency button is pressed, then we need to disable the defense mechanism,
             // including enabling classloading.
-            if (BYPASS)     return;
-
-            builder.withRemoteClassLoadingAllowed(false);
+            if (!BYPASS && BYPASS_LOG == null) {
+                builder.withRemoteClassLoadingAllowed(false);
+            }
+            // In either of the above cases, the check method will return normally, but may log things.
             builder.withRoleChecker(new CallableDirectionChecker());
         }
     }
1af<I>e8b7f<I>bca<I>d<I>b<I>e0fd<I>d3cb4e3 incorrectly disabled all logging.
When we are allowing all callables through, we want to enable remote class loading
(just in case someone is using it legitimately), but continue logging callable issues.
Currently there is no remoting flag to allow remote class loading while logging it.