pfstore(1)

πŸ“¦
version 1.6 Β· 2 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’– pfstore(1) πŸ’–

okay so bestie, welcome to pfstore β€” she lives in the General Commands Manual section and she is literally here to help you create and manage a pass-phrase store. slay. let's get into it πŸŽ€


✨ NAME ✨

pfstore β€” used to create and manage a pass-phrase store. that's it, that's the job, and she does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

pfstore [-n] [-d] -f pfsfile identity

πŸ¦‹ OPTIONS πŸ¦‹

  • -n β€” create the file. yes bestie, make it exist.
  • -d β€” delete the given identity from the store. bye bye πŸ‘‹
  • -f pfsfile β€” specifies the file that holds the identity/pass-phrase pairs. this is the file you're working with, no cap.

πŸ’œ DESCRIPTION πŸ’œ

pfstore is used to create and manage files that hold identity/pass-phrase pairs. her main character job? managing the owampd.pfs file for owampd. iconic honestly.

if the -d option is not specified, then pfstore prompts the caller for a pass-phrase. that pass-phrase gets hex-encoded and saved in the pfsfile alongside the associated identity. and listen β€” if the given identity already exists in the pfsfile, the previous pass-phrase gets overwritten with the new one. no hesitation, no drama, just replacement 🫢

pfsfiles generated by pfstore are formatted for use with OWAMP. periodt.


πŸŽ€ PFSFILE FORMAT πŸŽ€

pfstore generates lines of the format:

test 54b0c58c7ce9f2a8b551351102ee0938

so it's: an identity, followed by whitespace, followed by a variable-length hex-encoded pass-phrase. that's the whole vibe.

No other text is allowed on these lines. literally none. however πŸ’« comment lines may be added β€” and a comment line is any line where the first non-white space character is '#'. easy.


🌈 EXAMPLES 🌈

the classic

pfstore -f /etc/owampd/owampd.pfs testuser

adds a pass-phrase for the identity testuser. the user gets prompted for a pass-phrase. and btw β€” if the file does not exist, an error message will be printed and no action will be taken. πŸ™ˆ

the "make it first" one

pfstore -f /etc/owampd/owampd.pfs -n testuser

creates the file before doing the same as above. but if the file already exists, an error message will be printed and no action will be taken. so like, pick a lane bestie 😭

the "we're done here" one

pfstore -f /etc/owampd/owampd.pfs -d testuser

deletes the identity testuser from the pfsfile. and yeah β€” if the file does not exist, an error message will be printed and no action will be taken. same energy, same rule.


πŸ”₯ SECURITY CONSIDERATIONS πŸ”₯

okay this part is important so pay attention: the pass-phrases in the pfsfile are not encrypted in any way. they are simply hex-encoded. that's it. the security of these pass-phrases is completely dependent upon the security of the filesystem and the discretion of the system administrator.

bestie. hex-encoding is not encryption. anyone with the file has the tea. protect that filesystem like it's your notes app πŸ’€

⭐ RESTRICTIONS ⭐

identity names are restricted to 80 characters. that's the limit, don't push it.


πŸ‘‘ SEE ALSO πŸ‘‘

owping(1), owampd(1), owampd(1) and the http://e2epi.internet2.edu/owamp web site. (yes, owampd(1) is in there twice β€” she said it twice because she meant it twice πŸ’…)


πŸ’– ACKNOWLEDGMENTS πŸ’–

this material is based, in part, on work supported by the National Science Foundation (NSF) under Grant No. ANI-0314723. any opinions, findings, and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the NSF.


and that's the whole page bestie πŸ¦‹ this version is dated $Date$ and belongs to the pfstore(1) manual β€” thanks for reading, ily, go manage your pass-phrase store responsibly πŸ’œβœ¨

πŸ“¦ where this page comes from