CID / News: Recent posts

CID solves offline authentication failure in its new version!

---

The new CID version (1.1.3) has had its code adapted to work around the offline authentication failure issue in Debian-based distros (Bug #14618). The correction is done automatically and transparently for users, simply updating the software version to the latest one.

See complete changelog!

As of version 4.14.0, Samba started to support Group Policies (GPOs) for Linux clients.

---

For now, this support is limited to defining tasks in cron and applying sudo policies.

The CID has been adapted from version 1.1.3 to enable GPOs to run when CID logon scripts are enabled on the Linux computer. CID will also force the policies to be applied on every login of a AD user, as well as using the command to revert their settings if logon scripts will are disabled (see Change station behavior).... read more

Support for CID users will now be provided through the discussion forum and mailing list provided on the project page in SourceForge.

---

These tools are intended to improve and expand service capacity by sharing experiences more broadly and sharing the responsibility for support with other users willing to help this growing community day by day.... read more

CID corrected the problem of requesting authentication in CUPS print jobs for an SMB connection.

---

The solution found is based on the creation of a shell script that replaces the symbolic link usually created for smbspool binary in the CUPS backends directory. This script passes the print job arguments to smbspool, running it as the user owning the print job instead of root, which allows the process to use kerberos methods to authenticate the job.... read more

Soon, a new release of the program will be sent to mark a restart in the versioning.

---

Currently, versioning is based on two numeric fields (cid-x.x.tar.gz), with the first field (from left to right) changed when a major update was performed or a new feature was incremented. From now on, the program will have three fields in the version number beginning with version 1.0.0, and the variations will occur regardless of the content of the update and sequentially from the last field to the first one (from right to left), whenever a field to reach number nine.... read more