On 12/13/2016 03:20 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> The payload data may be stored in a tmpfs filesystem,
>> rather than in kernel memory, if the data size exceeds the
>> overhead of
On 12/13/2016 03:20 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> The payload data may be stored in a tmpfs filesystem,
>> rather than in kernel memory, if the data size exceeds the
>> overhead of storing the data in the
Michael Kerrisk (man-pages) wrote:
> The payload data may be stored in a tmpfs filesystem,
> rather than in kernel memory, if the data size exceeds the
> overhead of storing the data in the filesystem. (Storing
>
Michael Kerrisk (man-pages) wrote:
> The payload data may be stored in a tmpfs filesystem,
> rather than in kernel memory, if the data size exceeds the
> overhead of storing the data in the filesystem. (Storing
> the data in a
On 12/13/2016 02:38 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> So, I've updated this piece a couple of times since the draft that you
>> reviewed, and by now it reads:
>>
>>"big_key" (since Linux 3.13)
>> This key type is
On 12/13/2016 02:38 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> So, I've updated this piece a couple of times since the draft that you
>> reviewed, and by now it reads:
>>
>>"big_key" (since Linux 3.13)
>> This key type is similar to the "user" key
Hi David,
On 12/13/2016 02:31 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> I use/Linux man-pages uses the "Oxford comma" convention.
>
> "... an optional comma ..." ;-)
>
> There's also:
>
> ... LSM security checks are still performed, and
Hi David,
On 12/13/2016 02:31 PM, David Howells wrote:
> Michael Kerrisk (man-pages) wrote:
>
>> I use/Linux man-pages uses the "Oxford comma" convention.
>
> "... an optional comma ..." ;-)
>
> There's also:
>
> ... LSM security checks are still performed, and may filter out
>
Michael Kerrisk (man-pages) wrote:
> So, I've updated this piece a couple of times since the draft that you
> reviewed, and by now it reads:
>
>"big_key" (since Linux 3.13)
> This key type is similar to the "user" key type, but it may
>
Michael Kerrisk (man-pages) wrote:
> So, I've updated this piece a couple of times since the draft that you
> reviewed, and by now it reads:
>
>"big_key" (since Linux 3.13)
> This key type is similar to the "user" key type, but it may
> hold a payload of
Michael Kerrisk (man-pages) wrote:
> I use/Linux man-pages uses the "Oxford comma" convention.
"... an optional comma ..." ;-)
There's also:
... LSM security checks are still performed, and may filter out
further keys that the process is not authorized
Michael Kerrisk (man-pages) wrote:
> I use/Linux man-pages uses the "Oxford comma" convention.
"... an optional comma ..." ;-)
There's also:
... LSM security checks are still performed, and may filter out
further keys that the process is not authorized to view.
but has two
Hello David,
Amended a piece here after Eugene's note about encrypted keys.
On 13 December 2016 at 13:43, Michael Kerrisk (man-pages)
wrote:
> Hi David,
>
> On 12/13/2016 12:35 PM, David Howells wrote:
>> Michael Kerrisk wrote:
>>
>>>"big_key"
Hello David,
Amended a piece here after Eugene's note about encrypted keys.
On 13 December 2016 at 13:43, Michael Kerrisk (man-pages)
wrote:
> Hi David,
>
> On 12/13/2016 12:35 PM, David Howells wrote:
>> Michael Kerrisk wrote:
>>
>>>"big_key" (since Linux 3.13)
>>> This
Hi David,
On 12/13/2016 12:35 PM, David Howells wrote:
> Michael Kerrisk wrote:
>
>>The Linux key-management facility is primarily a way for driv‐
>>ers to retain or cache security data, authentication keys,
>>encryption keys, and other data in the
Hi David,
On 12/13/2016 12:35 PM, David Howells wrote:
> Michael Kerrisk wrote:
>
>>The Linux key-management facility is primarily a way for driv‐
>>ers to retain or cache security data, authentication keys,
>>encryption keys, and other data in the kernel.
>
> No
Michael Kerrisk wrote:
>The Linux key-management facility is primarily a way for driv‐
>ers to retain or cache security data, authentication keys,
>encryption keys, and other data in the kernel.
No comma before "and".
>access to the
Michael Kerrisk wrote:
>The Linux key-management facility is primarily a way for driv‐
>ers to retain or cache security data, authentication keys,
>encryption keys, and other data in the kernel.
No comma before "and".
>access to the facility. See
Hi David,
Would you have a chance to look at this page?
Cheers
Michael
On 11/04/2016 04:47 PM, Michael Kerrisk wrote:
> Hi David,
>
> As part of the process of adopting the *.7 pages from
> keyutils into man-pages, I've made some significant
> extensions to the keyrings(7) page. Among the
Hi David,
Would you have a chance to look at this page?
Cheers
Michael
On 11/04/2016 04:47 PM, Michael Kerrisk wrote:
> Hi David,
>
> As part of the process of adopting the *.7 pages from
> keyutils into man-pages, I've made some significant
> extensions to the keyrings(7) page. Among the
Hi David,
As part of the process of adopting the *.7 pages from
keyutils into man-pages, I've made some significant
extensions to the keyrings(7) page. Among the more notable
changes:
* Expanded the detail in "Key types"
* Addition of a section on the various /proc files
* Various other minor
Hi David,
As part of the process of adopting the *.7 pages from
keyutils into man-pages, I've made some significant
extensions to the keyrings(7) page. Among the more notable
changes:
* Expanded the detail in "Key types"
* Addition of a section on the various /proc files
* Various other minor
22 matches
Mail list logo