problems with fd
I take that back, I did upgrade from 1.06 to 1.07 since then. That would appear to have triggered this.
-----Original Message-----
From: Ryan Bergauer [mailto:[email protected]]
Sent: Friday, August 09, 2002 4:49 PM
To: '[email protected]'
Subject: problems with fd
I'm getting a particular denied message in quite a few places.
The scontext is always the program's context, as in user_name:user_r:user_gpg_t.
The tcontext is how I got my current role, as in user_name:sysadm_r:newrole_t or system_u:system_r:local_login_t. It's denying the use of fd.
This just popped up - I know I've used GPG before, but never had this error. Any suggestions?
-Ryan
Quoted 2 lines · Ryan Bergauer
I take that back, I did upgrade from 1.06 to 1.07 since then. That would appear to have triggered this.
An upgrade of gpg does not make any difference, all versions of gpg work in the same way in this regard. Unless however you forgot to relabel the new gpg after the upgrade and as a result have the gpg process running in a different domain.
Quoted 8 lines
The scontext is always the program's context, as in user_name:user_r:user_gpg_t.
The tcontext is how I got my current role, as in user_name:sysadm_r:newrole_t or system_u:system_r:local_login_t. It's denying the use of fd.This just popped up - I know I've used GPG before, but never had this error. Any suggestions?
Please tell me exactly what you are doing with gpg?
I've just done a quick test and I can't trigger such problems with my policy.
Please tell me the exact type of gpg command and how you run it (from xterm
or console, etc), and which role you are using. Then I'll try and reproduce the problem.
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
The gpg command in question is 'gpg --gen-key', being run from the console as (in the case of system_u:system_r:local_login_t) a normal user in user_r and (in the case of user_name:sysadm_r:newrole_t) a sysadm that newroled into the user_r role.
-----Original Message-----
From: Russell Coker [mailto:[email protected]]
Sent: Friday, August 09, 2002 5:13 PM
To: Ryan Bergauer; [email protected]
Subject: Re: problems with fd
Quoted 1 line · Ryan Bergauer
I take that back, I did upgrade from 1.06 to 1.07 since then. That
would
Quoted 1 line
appear to have triggered this.
An upgrade of gpg does not make any difference, all versions of gpg work in
the same way in this regard. Unless however you forgot to relabel the new
gpg after the upgrade and as a result have the gpg process running in a different domain.
Quoted 8 lines
The scontext is always the program's context, as in user_name:user_r:user_gpg_t.
The tcontext is how I got my current role, as in user_name:sysadm_r:newrole_t or system_u:system_r:local_login_t. It's denying the use of fd.This just popped up - I know I've used GPG before, but never had this error. Any suggestions?
Please tell me exactly what you are doing with gpg?
I've just done a quick test and I can't trigger such problems with my policy.
Please tell me the exact type of gpg command and how you run it (from
xterm
or console, etc), and which role you are using. Then I'll try and reproduce
the problem.
Signature · 3 lines
I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the
Quoted 1 line
From field.
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.
Quoted 4 lines · Ryan Bergauer
The gpg command in question is 'gpg --gen-key', being run from the console as (in the case of system_u:system_r:local_login_t) a normal user in
user_rand (in the case of user_name:sysadm_r:newrole_t) a sysadm that newroled into theuser_rrole.
allow $1_gpg_t privrole:fd use;
I was not able to reproduce the problem with local_login_t. I was able to reproduce the problem with newrole_t and added the above rule in the gpg_domain() macro in the policy/macros/program/gpg_macros.te file to solve it.
Russell Coker
--
This message was distributed to subscribers of the selinux mailing list. If you no longer wish to subscribe, send mail to [email protected] with the words "unsubscribe selinux" without quotes as the message.