• Public documentation, introduction and practices page.

It has come to my understanding that PaperCut plans to use Silver in an upcoming release (~1 year). I was told that the idea behind Silver and the product it will be included in is to "host an agent service installed at customer sites that needs to operate reliably with zero on-site maintenance and configuration." Unfortunately, this is not easily done. Here is my take on the security of Silver. This basic, common mistake that most software makes is that it updates over HTTP (or binaries are distributed over HTTP). However, Silver takes that a step further by allowing arbitrary command injection. Read more here.

Build process should build both 32-bit and 64-bit, and clearly label.

"note" ==> "not"

I met a problem about silver and had been trying two day without progress.

I got the source of silver, alse setup go lang in my pc.

Then I executed "go run make.go setup" without any error, when I executed "go run make.go",

The error msg was "Godeps_workspace\src\code.google.com\p\winsvc\mgr\service.go:8:2: C source files not allowed when not using cgo: sys.c."

I set CGO_ENABLED=1 ,but it didn't work.

Using cgo seems necessary during "go run make.go", but I could not how to use cgo, are there any clue for solving it?

Windows edition : Windows 7 ultimate 32 bit

This is my environment varibles in pc.
-----------------env begin-------------------
set GOARCH=386
set GOBIN=
set GOCHAR=8
set GOEXE=.exe
set GOHOSTARCH=386
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\go_path;D:\mygo;
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_386
set CC=gcc
set GOGCCFLAGS=-m32 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
-----------------env end-------------------

Always should be an ongoing focus... but we can do a bit better now.

Add support to "include" config from other locations or versioned subdirectories. This will allow application configuration to evolve over time with updates.

Seems to be some intermittent termination issues on Windows.

• Review of config labels:
  • *Timeout has no time units
  • Is seconds the right resolution?
• Need to document update JSON format used for update.exe - top of file?
• Upgrade checksums - remove MD5? Secure?
• Certificate enforcement in update check - lock to a domain
• .reload vs .restart ?
• Review check check "operations". The name "actions" and "args" seem inconsistent.

In startServices : main.go. Runconfig.GracefulShutdownTimeoutSecs is not set.

Meaning the default is always used, not the GracefulShutdownTimeoutSec from the config.

sc.RunConfig.GracefulShutdownTimeoutSecs = service.GracefulShutdownTimeout