All of lore.kernel.org
 help / color / mirror / Atom feed
From: zhaoshuo <zhaoshuo@cqsoftware.com.cn>
To: Alex Shi <seakeel@gmail.com>
Cc: alexs@kernel.org, si.yanteng@linux.dev, corbet@lwn.net,
	zhaoyuehui@cqsoftware.com.cn, zhangwei@cqsoftware.com.cn,
	maoyuxian@cqsoftware.com.cn, linux-doc@vger.kernel.org
Subject: Re: [PATCH] docs/zh_CN: Add security credentials Chinese translation
Date: Tue, 7 Jan 2025 13:53:12 +0800	[thread overview]
Message-ID: <551c040d-4331-4f05-a690-ed1cd2e28490@cqsoftware.com.cn> (raw)
In-Reply-To: <CAJy-AmmhXThUa3yU4Rc_o8abP06E8MypKTdrcZv6U8Z6A9co-g@mail.gmail.com>


在 2025/1/7 13:22, Alex Shi 写道:
> Shuo Zhao <zhaoshuo@cqsoftware.com.cn> 于2025年1月3日周五 14:15写道:
> ...
>
>> +
>> + 3. 客观上下文
>> +
>> +        此外在这些对象的凭据中,将有一个子集表示对象的“客观上下文”。
>> +        这可能与(2)中相同,也可能不同 —— 例如,在标准的UNIX文件中,
>> +        这是由标记在索引节点上的UID和GID定义的。
>> +
>> +        客观上下文是进行安全计算的一部分,当对象被操作时会用到。
>> +
> ...
>
>> +
>> + 5. 主观上下文
>> +
>> +        主体对其凭据有一个额外的解释。其凭据的一个子集形成了“主观上下文”。主观
>> +        上下文在主体执行操作时作为安全计算的一部分使用。
>> +
>> +        例如,Linux任务在操作文件时会有FSUID、FSGID和附加组列表 —— 这些凭据
>> +        与通常构成任务的客观上下文的真实UID和GID是相互独立的。
>> +
> Anyway, I'm still confused on the 客观 and 主观 context, translation. Is
> it better to use
> 对象上下文, 主体上下文?
> No idea.

Yes, this seems to correspond better with the previous text.


Thanks,

ZhaoShuo


  reply	other threads:[~2025-01-07  6:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-03  6:15 [PATCH] docs/zh_CN: Add security credentials Chinese translation Shuo Zhao
2025-01-07  5:22 ` Alex Shi
2025-01-07  5:53   ` zhaoshuo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-14  2:28 Shuo Zhao
2025-02-04 17:03 ` Jonathan Corbet

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=551c040d-4331-4f05-a690-ed1cd2e28490@cqsoftware.com.cn \
    --to=zhaoshuo@cqsoftware.com.cn \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=maoyuxian@cqsoftware.com.cn \
    --cc=seakeel@gmail.com \
    --cc=si.yanteng@linux.dev \
    --cc=zhangwei@cqsoftware.com.cn \
    --cc=zhaoyuehui@cqsoftware.com.cn \
    /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.