atlassian Bamboo에서 실행할 때 signtool 설치 프로그램에 서명하지 못합니다.

Question

내부 보안 조치를 위해 Bamboo에서 코드 서명을 자동화하려고합니다.

서명 명령 : 나는 .PFX 형태로 우리의 IT 부서에서 내부적으로 생성 된 인증서를 사용하고

signtool.exe sign /v /debug /f "\\hostname\Cert$\Cerfile.pfx" /p "password" /d "Company name" /t "http://timestamp.verisign.com/scripts/timstamp.dll" "c:\test\installer.msi" 

.

검증 :

signtool verify /pa "c:\test\installer.msi" 

두 명령은 내가 로컬 컴퓨터 (동일한 사용자 대나무 서비스 사용자로) 명령 창에서 실행하면 완벽하게 정상적으로 작동합니다. 이 스크립트를 Atlassian Bamboo에서 스크립트 작업으로 실행할 때 실패합니다.

"추가 저장 완료"에서 중지됩니다. 이 후에는 오류 또는 성공 메시지가 표시되지 않습니다.

아래 서명이 성공적으로 끝나면 로컬 호스트에서 실행 중입니다.

......... 
Done Adding Additional Store 
Successfully signed: c:\test\installer.msi 

Number of files successfully Signed: 1 
Number of warnings: 0 
Number of errors: 0 

이것은 Bamboo에서 동일한 명령을 실행하면 나타납니다.

build 20-Jan-2017 08:05:07 The following certificates were considered: 
build 20-Jan-2017 08:05:07  Issued to: RnD Software Engineering 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued by: <....> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Expires: <...........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  SHA1 hash: <...........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued to: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued by: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Expires: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  SHA1 hash: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued to: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued by: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Expires: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  SHA1 hash: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07 After EKU filter, 3 certs were left. 
build 20-Jan-2017 08:05:07 After expiry filter, 3 certs were left. 
build 20-Jan-2017 08:05:07 After Private Key filter, 1 certs were left. 
build 20-Jan-2017 08:05:07 The following certificate was selected: 
build 20-Jan-2017 08:05:07  Issued to: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued by: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Expires: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  SHA1 hash: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07 The following additional certificates will be attached: 
build 20-Jan-2017 08:05:07  Issued to: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Issued by: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  Expires: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  SHA1 hash: <........> 
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07  
build 20-Jan-2017 08:05:07 Done Adding Additional Store 

은 검증은 어떤 도움을 주시면 더 좋구요

build 20-Jan-2017 08:05:07 File: c:\abc\installer.msi 
build 20-Jan-2017 08:05:07 Index Algorithm Timestamp  
build 20-Jan-2017 08:05:07 ======================================== 
build 20-Jan-2017 08:05:08  
build 20-Jan-2017 08:05:08 Number of errors: 1 
error 20-Jan-2017 08:05:08 SignTool Error: No signature found. 

를 기록합니다.

Answer 1

다른 타임 스탬프 서버를 사용하여 문제를 해결할 수있었습니다. 아래 명령은 Bamboo 인라인 스크립트 작업에서 작동했습니다.

signtool.exe sign /v /debug /f "\\hostname\Cert$\Cerfile.pfx" /p "password" /d "Company name" /tr "http://sha1timestamp.ws.symantec.com/sha1/timestamp" "c:\test\installer.msi"