Open odisseus opened 4 years ago
It turns out that the problem was caused by a bad entry in the global policy configuration:
0WdAKHigtwbDdi0mhDKcLy6gKNhPBw6K6crBww7ZiSI scope ProjectScope unicorn
permission className java.util.PropertyPermission
target \*
action Some read,write
The wildcards have different effect if Fury is invoked in standalone mode:
$ set -o noglob
$ fury permission require -C java.util.PropertyPermission -T * -A 'read,write'
54bb16098c4d5d4efcbc86a4f7c00b9976dce7a038ca719ea693bfd1a50bf966
$ fury standalone permission require -C java.util.PropertyPermission -T * -A 'read,write'
2614b50c9de54c3c2fb2160fd103c3c3bb7838a20ac665e84fa55e3eee0a1f8d
$ fury permission list
~/devel/virtus_fury/beholder/test
HASH CLASS TARGET ACTION
261 java.util.PropertyPermission * read,write
54b java.util.PropertyPermission README.md read,write
Example
Command
Entry in the layer file
Entry in the permissions list
Stack trace
Generated entry in the policy file