You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. I'm packaging this for Debian, and we are going through license statements. The pemutil/ssh.go file begins with:
// Copyright 2012 The Go Authors. All rights reserved.
// Use of this source code is governed by a BSD-style
// license that can be found in the LICENSE file.
But I cannot find this file in this package. Could you add it, or at least qualify which license applies to this work? "BSD-style" is not universially unambigious, and having clear licensing matters to Debian.
Your Environment
Debian
Expected Behavior
Appropriate LICENSE file included
Actual Behavior
Appropriate LICENSE file missing
Additional Context
No response
Contributing
No response
The text was updated successfully, but these errors were encountered:
I added the header and the comment because I got the definition of the structure openSSHPrivateKey and the magic header from x/crypto/ssh. I did that because I needed to detect whether a key was password-protected.
In fact, I also moved those structs in x/crypto/ssh from anonymous structs to named ones. I did that because I implemented ssh.MarshalPrivateKey and ssh.MarshalPrivateKeyWithPassphrase from my own implementation of pemutil.SerializeOpenSSHPrivateKey.
I think it is safe to remove or ignore that header. I'm raising this question to confirm that I can remove the comment.
Steps to Reproduce
Hi. I'm packaging this for Debian, and we are going through license statements. The pemutil/ssh.go file begins with:
But I cannot find this file in this package. Could you add it, or at least qualify which license applies to this work? "BSD-style" is not universially unambigious, and having clear licensing matters to Debian.
Your Environment
Debian
Expected Behavior
Appropriate LICENSE file included
Actual Behavior
Appropriate LICENSE file missing
Additional Context
No response
Contributing
No response
The text was updated successfully, but these errors were encountered: