foobar0815 / gosignature Goto Github PK

Hi,

I have the problem that the German letters öäü do not show correctly (That comes from the Active Directory)
I have checked that the template is in utf-8. It wasn't. So I changed it, but now the German letters from the template always not shown correctly.
Can someone say me what I do wrong?

At the moment, ini files need to sit below the program's directory: "Settings for -ini are relative to the program's base directory.".
This was confusing me in the beginning (not having read that info, yet).

Therefore, I cannot split program and data which in some cases might be useful.
gosignature should be able to recognize wether an absolute path is used and handle this accordingly.

Didn't want to install Go on my laptop, but had a Linux VM available. Thought this might be interesting to others.

According to https://stackoverflow.com/a/74049924/1139088, you will at least need go 1.17 to prevent errors like "undefined: unsafe.Add". These instructions use Debian Bookworm (Debian Bullseye should be possible using the backports repository).

• Install packages

apt install golang-go git

• Clone repository

git clone "https://github.com/foobar0815/gosignature.git" && cd gosignature

• Fix problems (go: cannot find main module, but found .git/config in ...)

go mod init gosignature

• Get dependencies

go get golang.org/x/sys/windows/registry
go get golang.org/x/text/encoding/charmap
go get gopkg.in/ini.v1
go get github.com/go-ldap/ldap/v3

• Fix "ldap.go:6:2: no required module provides package gopkg.in/ldap.v3" (seems to have been moved/renamed)

sed -i 's:gopkg.in/ldap.v3:github.com/go-ldap/ldap/v3:' ldap.go

• Compile for windows (while reducing binary size)

GOOS=windows GOARCH=amd64 go build -o gosignature.exe -ldflags="-s -w"

If you have e.g. the mobile phone number in the signature, then every employee who doesn't have a phone have an "empty" signature line

Template:

...
Phone: @PHONE@
Mobile: @MOBILE@
E-Mail: @EMAIL@
...

Generated:

...
Phone: 12345678
Mobile:
E-Mail: [email protected]

It would be cool, if this tool removes every line which actual value is empty.

At the moment, the available params are not explained in the docs (where I'd look first).

Would be useful to at least have an info about using "-help" to get an usage overview.

I got this error:

ERROR: LDAP Result Code 206 "Empty password not allowed by the client": ldap: empty password not allowed by the client

With OutlookSignature, it wasn't necessary to explicitly specify LDAP credentials as OutlookSignature was simply using the logged in user's credentials (afaik).

Config looked like this:

LDAPReaderAccountName=
LDAPReaderAccountPassword=
LDAPUserFieldname=sAMAccountName

Would be nice if gosignature could do it the same.

"Relying on a GPO for setting the default signature on a company wide level should be preferred over the software's approach to manipulate the user's registry."

Could you please link this to some helpful information?
(Was not able to find something useful (and no, not searching for too long ;-) ))