From: "cto@itechfrontiers.com" <cto@itechfrontiers.com>
To: Cliffe <cliffe@ii.net>
Cc: Behnaz Hassanshahi <behnaz.kallen@yahoo.com>,
SELinux <selinux@tycho.nsa.gov>
Subject: Re: temporal role base access control in Linux
Date: Sun, 07 Nov 2010 11:31:16 -0500 [thread overview]
Message-ID: <4CD6D454.3040709@itechfrontiers.com> (raw)
In-Reply-To: <4CD6C7B0.90305@ii.net>
Hello Cliffe,
I Believe, I provided enough information to be able to achieve what has
been asked here.
Anyway I'm bound to the US rules and abide and respect them, and
definitely am not a Lawyer, however my concern was not EAR (Export
Administration Regulations) the law is much more complicated than just
an export control regulation,
By considering the source of the message coming from a known University
in Iran working on dual purpose subjects, I personally prefer not to
help particularly (on implementation basis), and I think I have such right.
Tried to help as much as I could.
Providing legal advice requires attorney-client privilege/relationship
and I don't think just Google search result would be enough in such case.
Anyway this is not a legal mailing list, technical aspects have been
covered as much as it should, if you would like you may add additional
notes.
Best Regards,
Patrick K.
On 11/7/2010 10:37 AM, Cliffe wrote:
> On 7/11/2010 10:39 PM, cto@itechfrontiers.com wrote:
>> I'm sorry but with all due respects, I don't know if helping people in
>> Iran on the subject is legal or not (I'm not a Lawyer) but judging
>> from sources of your mail (which is Iran), I prefer not to be involved
>> in any particular help.
> I have never heard anything that has suggested that there have ever been
> US export laws regarding access control software, let alone helping
> someone set up their free open source security software (please let me
> know if you have heard otherwise). It has been 10 years since US
> cryptography export laws have relaxed (and maybe they still apply to
> embargoed destinations).
>
> Just a quick google:
> "controls on encryption did not apply to cryptographic equipment and
> software if their functionality was limited to any of the following nine
> categories:" ... "(5) Access control devices such as ATMs;"
>> Anyway this is a project develped primarily by the National Security
>> Agency of the USA, and its contributors.
> That does not seem relevant to me...
>
> Cliffe.
>
>
>
> --
> This message was distributed to subscribers of the selinux mailing list.
> If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov
> with
> the words "unsubscribe selinux" without quotes as the message.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-11-07 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-07 12:20 temporal role base access control in Linux Behnaz Hassanshahi
2010-11-07 14:39 ` cto
2010-11-07 15:37 ` Cliffe
2010-11-07 16:31 ` cto [this message]
2010-11-07 16:50 ` Cliffe
2010-11-07 17:44 ` cto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CD6D454.3040709@itechfrontiers.com \
--to=cto@itechfrontiers.com \
--cc=behnaz.kallen@yahoo.com \
--cc=cliffe@ii.net \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.