Re: Revised add_key(2) man page for review

Hi Eugene, On 13 December 2016 at 13:06, Eugene Syromyatnikov wrote: > On Tue, Dec 13, 2016 at 11:49 AM, Michael Kerrisk (man-pages) > wrote: >> On 13 December 2016 at 12:37, David Howells wrote: >>> Michael Kerrisk (man-pages)

Re: Revised add_key(2) man page for review

Hi Eugene, On 13 December 2016 at 13:06, Eugene Syromyatnikov wrote: > On Tue, Dec 13, 2016 at 11:49 AM, Michael Kerrisk (man-pages) > wrote: >> On 13 December 2016 at 12:37, David Howells wrote: >>> Michael Kerrisk (man-pages) wrote: >>> > "stored encrypted in swap space".

Re: Revised add_key(2) man page for review

On Tue, Dec 13, 2016 at 11:49 AM, Michael Kerrisk (man-pages) wrote: > On 13 December 2016 at 12:37, David Howells wrote: >> Michael Kerrisk (man-pages) wrote: >> >>> > "stored encrypted in swap space". >>> >>> Fixed. >> >>

Re: Revised add_key(2) man page for review

On Tue, Dec 13, 2016 at 11:49 AM, Michael Kerrisk (man-pages) wrote: > On 13 December 2016 at 12:37, David Howells wrote: >> Michael Kerrisk (man-pages) wrote: >> >>> > "stored encrypted in swap space". >>> >>> Fixed. >> >> Since 4.8, that is. > > Which commit was that? I could not find it?

Re: Revised add_key(2) man page for review

On 13 December 2016 at 12:37, David Howells wrote: > Michael Kerrisk (man-pages) wrote: > >> > "stored encrypted in swap space". >> >> Fixed. > > Since 4.8, that is. Which commit was that? I could not find it? -- Michael Kerrisk Linux man-pages

Re: Revised add_key(2) man page for review

On 13 December 2016 at 12:37, David Howells wrote: > Michael Kerrisk (man-pages) wrote: > >> > "stored encrypted in swap space". >> >> Fixed. > > Since 4.8, that is. Which commit was that? I could not find it? -- Michael Kerrisk Linux man-pages maintainer;

Re: Revised add_key(2) man page for review

Michael Kerrisk (man-pages) wrote: > > "stored encrypted in swap space". > > Fixed. Since 4.8, that is. David

Re: Revised add_key(2) man page for review

Michael Kerrisk (man-pages) wrote: > > "stored encrypted in swap space". > > Fixed. Since 4.8, that is. David

Re: Revised add_key(2) man page for review

Hello David Thanks for the review! On 12/13/2016 11:58 AM, David Howells wrote: > Michael Kerrisk (man-pages) wrote: > >>The destination keyring serial number may be that of a valid >>keyring for which the caller has write permission, or it may be >>

Re: Revised add_key(2) man page for review

Hello David Thanks for the review! On 12/13/2016 11:58 AM, David Howells wrote: > Michael Kerrisk (man-pages) wrote: > >>The destination keyring serial number may be that of a valid >>keyring for which the caller has write permission, or it may be >>one of the

Re: Revised add_key(2) man page for review

Michael Kerrisk (man-pages) wrote: >The destination keyring serial number may be that of a valid >keyring for which the caller has write permission, or it may be >one of the following special keyring IDs: No comma before "or". >"user"

Re: Revised add_key(2) man page for review

Michael Kerrisk (man-pages) wrote: >The destination keyring serial number may be that of a valid >keyring for which the caller has write permission, or it may be >one of the following special keyring IDs: No comma before "or". >"user" This is a general

Revised add_key(2) man page for review

Hi David (and anyone else with an interest to review) Following on from the request_key(2) page that I already posted, I've pasted the current draft of the add_key(2) below. The changes to this page are less wide-ranging than for request_key(2), but you may also have suggestions for further

Revised add_key(2) man page for review

Hi David (and anyone else with an interest to review) Following on from the request_key(2) page that I already posted, I've pasted the current draft of the add_key(2) below. The changes to this page are less wide-ranging than for request_key(2), but you may also have suggestions for further