2000
DOI: 10.17487/rfc2847
|View full text |Cite
|
Sign up to set email alerts
|

LIPKEY - A Low Infrastructure Public Key Mechanism Using SPKM

Abstract: Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0

Year Published

2003
2003
2018
2018

Publication Types

Select...
4
2

Relationship

0
6

Authors

Journals

citations
Cited by 7 publications
(4 citation statements)
references
References 15 publications
0
4
0
Order By: Relevance
“…The GSS API, which is apparently becoming standard for the security in the file systems, is present in the mainline kernel, but the support of a public key infrastructure is somewhat limited. There is no support for the LIPKEY [7] implementation and the SPKM [1] implementation relies on a user space helper process that is a part of the NFS bundle (it is a part of the nfs-util package). For that reason, the GSS API has not been chosen, though it may be reconsidered in a future, when GSS becomes more widely supported.…”
Section: Methodsmentioning
confidence: 99%
“…The GSS API, which is apparently becoming standard for the security in the file systems, is present in the mainline kernel, but the support of a public key infrastructure is somewhat limited. There is no support for the LIPKEY [7] implementation and the SPKM [1] implementation relies on a user space helper process that is a part of the NFS bundle (it is a part of the nfs-util package). For that reason, the GSS API has not been chosen, though it may be reconsidered in a future, when GSS becomes more widely supported.…”
Section: Methodsmentioning
confidence: 99%
“…It increases the protection security of the data and also provides nature or characteristics of the data to be factored for security. But when considering the real time factors involved in the data transmission setting, this broad regulation often proves to be not viab le [7]. For the selection of suitable encryption points, the following parameters and impacts shall be well thought out for the selection procedures.…”
Section: Encryption Pointmentioning
confidence: 99%
“…Strong security has not been available until the latest version (V4 [40]), which mandates the support of the RPCSEC_GSS flavor [14]. RPCSEC_GSS provides RPC-layer security based on the GSS-API [30], and a conforming NFS V4 implementation must support two security mechanisms, Kerberos V5 [31] and LIPKEY [13].…”
Section: Secure Distributed File Systemmentioning
confidence: 99%