IETF-SSH archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: PublicKeyFile Format Security Considerations




On Friday, Jul 25, 2003, at 19:25 America/Montreal, Bill Sommerfeld wrote:
  The file format described by this document provides no mechanism
  to verify the integrity or otherwise detect tampering of the
  data stored in such files. It is the responsibility of the parties
  that create or exchange files written in this format to ensure that
  appropriate access controls are applied to such files, and that
  the files, if transfered, are exchanged over a trusted channel.

  The data encoded using this file format is sensitive.

"sensitive" in what sense?

  Implementors are cautioned to verify the correctness of the
  encoding/decoding routines used to save and read files in this
  format. A malfunctioning decoder used to read a public-key file
  will most likely produce unsound data of unknown cryptographic
  properties that in the worst case could be vulnerable various
  forms of cryptographic attack.

Suggested text fragment:

	"Given the potential of an adversary tampering with data stored
	in such files on filesystems, system-specific measures (e.g.
	Access Control Lists, UNIX permissions, other Discretionary
	and/or Mandatory Access Controls) SHOULD be used to protect
	these files."

(edit to taste)

Ran




Home | Main Index | Thread Index | Old Index