hclnotes.txt

来自「伯克利做的SFTP安全文件传输协议」· 文本 代码 · 共 26 行

Notes on interoperability with HCL inetd
----------------------------------------

Since the daemon user is separate, networked drives don't work,
since that is a per-user configuration.  Instead, physical
drives must be used if the file is local.  For network, perhaps
UNC names work?  Didn't try it.

Connection logging is quite useful for initial diagnostics.
In particular, if it can't find the executable, it logs Error 2,
which corresponds to ENOFILE (file not found).

Event numbers (in Event Viewer):
  100     service disable from Control Panel
  105     service enable, either from Control Panel, or after 112
  106     incoming connection
  112     restarting listen, called when shutdown received by inetd,
          and followed by a 105

The hcl-started daemons run as "SYSTEM", which means the same privilege
as the other OS kernel components.  Therefore, getting a secure place to
store data is just a matter of creating a directory or registry key for
which "Everyone" does *not* have access.  Since "SYSTEM" always does,
that's all it takes.