On Wed, May 08, 2019 at 01:04:02PM -0400, mark wrote:
> Hmmm, didn't complain when I did that... but they're still bin_t, not lib_t.
'semanage fcontext ...' updates the policy, but doesn't actually
change the context on the paths (which may or may not even exist at
the time the command runs).
On May 8, 2019, at 11:44 AM, mark wrote:
>
> Warren Young wrote:
>> On May 8, 2019, at 11:04 AM, mark wrote:
>>
>>>
>>> semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so”
>>
>> Glob expansion doesn’t happen in double quotes. Not in Bash, anyway.
>
> Huh? I thought it didn't occur
Warren Young wrote:
> On May 8, 2019, at 11:04 AM, mark wrote:
>
>>
>> semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so”
>
> Glob expansion doesn’t happen in double quotes. Not in Bash, anyway.
Huh? I thought it didn't occur in single quotes, but did occur in quotes.
Odd, I'm seeing
On May 8, 2019, at 11:04 AM, mark wrote:
>
> semanage fcontext -m -t lib_t "/path/smwa/webagent/bin/*.so”
Glob expansion doesn’t happen in double quotes. Not in Bash, anyway.
___
CentOS mailing list
CentOS@centos.org
Warren Young wrote:
> On May 8, 2019, at 9:31 AM, mark wrote:
>
>> semanage -fcontext -a -t lib_t "//smwa/webagent/bin(/.*).so”
>
> [snip]
>
>> What am I doing wrong?
>>
> Also, I’m confused by the parens in your file path. Whether your shell
> is or not is a different question.
I'm following
On May 8, 2019, at 9:31 AM, mark wrote:
>
> semanage -fcontext -a -t lib_t "//smwa/webagent/bin(/.*).so”
[snip]
> What am I doing wrong?
-fcontext isn’t an option, it’s a verb; drop the dash.
Also, I’m confused by the parens in your file path. Whether your shell is or
not is a different
We're forced to use Siteminder, by CA, who have no clue what they're doing
in *nix. No packages, tarballs...
Anyway, I'm trying clean up some stuff, and in /*/smwa/webagent/bin (all
their binaries, including .so's, are in there, duh... I'm trying to set
the .so's to lib_t.
semanage -fcontext -a
7 matches
Mail list logo