Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ryIsT-00FWLJ-Ej for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 20 Apr 2024 22:08:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ryIsR-00CAEu-KT for pgsql-pkg-yum@arkaria.postgresql.org; Sat, 20 Apr 2024 22:08:07 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ryIsR-00CAEm-3k for pgsql-pkg-yum@lists.postgresql.org; Sat, 20 Apr 2024 22:08:07 +0000 Received: from 008.lax.mailroute.net ([199.89.1.11]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ryIsM-003pHS-Td for pgsql-pkg-yum@postgresql.org; Sat, 20 Apr 2024 22:08:05 +0000 Received: from localhost (localhost [127.0.0.1]) by 008.lax.mailroute.net (Postfix) with ESMTP id 4VMQcd4WLTz6Cnk9B for ; Sat, 20 Apr 2024 22:08:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=acm.org; h= content-transfer-encoding:content-type:content-type:mime-version :user-agent:date:date:message-id:subject:subject:from:from :received:received; s=mr01; t=1713650880; x=1716242881; bh=IfsBB anZaE8MUE/xeHXcqVpNoGz7mNd9O06TASWdtJw=; b=SX2qZp+O8caYOkuLy6zC+ gfeE2FckdtudVyNYhAawxRvH33y23ZuC8HFzA67CeR3jYSR0yxlOHi4wFbDIoXbH e37MssHMzucevL0tNoQg+/xwwxiI/uQp2VKHnXoXSfILncINAg8yjG8yaARynq9f alOW20YERlSRzlioZ4k0GKkHe8qdp4YEQinz55KzCmzmYUYCHvuRgOHzRLjPKeS5 lodjERsjHwofgFDAbB5Gv++XDSQGmXtlj5sA29kVmEo7VZLZ0veBRHbdgRMVI++M C3ZizVtX1l7/ltFcs1Zj+zdgjT7rpPeLK8F6T/TfXMapN0OMCJUUnb+WldC0KuV7 A== X-Virus-Scanned: by MailRoute Received: from 008.lax.mailroute.net ([127.0.0.1]) by localhost (008.lax [127.0.0.1]) (mroute_mailscanner, port 10029) with LMTP id jCyU836RugOX for ; Sat, 20 Apr 2024 22:08:00 +0000 (UTC) Received: from [73.103.120.3] (c-73-103-120-3.hsd1.in.comcast.net [73.103.120.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jcflack@acm.org) by 008.lax.mailroute.net (Postfix) with ESMTPSA id 4VMQcc4cYdz6Cnk98 for ; Sat, 20 Apr 2024 22:08:00 +0000 (UTC) From: Chapman Flack X-Enigmail-Draft-Status: N1110 Subject: pljava rpm package missing pljava.policy file? To: pgsql-pkg-yum@postgresql.org Message-ID: <66243CBE.30509@acm.org> Date: Sat, 20 Apr 2024 18:07:58 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, I was recently responding to a puzzling blog post by Luca Ferrari about installing PL/Java on Rocky Linux, where he'd made a strange comment about needing to add a grant of AllPermission in Java's own systemwide default policy file before PL/Java would even run! I responded that if any adjustments to PL/Java's policy were needed, they should have been made in $(pg_config --sysconfdir)/pljava.policy However, there seems to be a worse problem that wasn't his fault. If I am looking in the right pljava.spec file ... https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/main/non-common/pljava/main/pljava.spec;hb=HEAD ... it seems not to include pljava.policy in the rpm at all. No wonder Luca struggled to make it work. I wonder how many have tried to use this rpm package since 1.6.0 and also struggled the same way, or given up. Can the pljava.policy file be included in the rpm? Thanks! Regards, -Chap