Re: A plugin to record modification timestamp and modifiers DN for specific attribute

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On 19 Sep 2020, at 01:15, Jan Tomasek <jan@xxxxxxxxxx> wrote:
> 
> Hi William,
> 
> On 9/9/20 2:31 AM, William Brown wrote:
>>> I need to keep track when and by whom was entryStatus attribute
>>> modified. For those informations, we have two attributes
>>> entryStatusTimestamp and entryStatusModifier attributes. And every time
>>> entryStatus is changed, our plugin changes automatically those two
>>> attributes.
>>> 
>>> Is there any standard, or maybe some contributed plugin how I can
>>> achieve this?
>> 
>> Sadly, I can't think of anything that exists today that achieves what you want, so I think you'll need to stick with this.
> 
> After some debugging I've identified the problem, it was not caused by
> incompatibility with never 389DS, but by weird config syntax requiring
> TAB characters. Which I lost during Copy&Paste. :(
> 
> In case anyone is interested I've published it:
> 	https://github.com/CESNET/389ds-plugin-ssm
> 
> I can't say it's nice code and repository isn't clean, there are some
> unused files related to OTP which was used at FEL CTU, in time strong
> crypto export from USA to our country was prohibited. But still it might
> be interesting for someone...

Thanks for making it public! It's not often that we get to see some of the cool plugins that people make for 389, and the features they bring.

An interesting idea that could bring you a lot assurance, would be to integrate and test with Address Sanitiser. This would help you find and detect potential memory safety issues in the plugin. If you want some advice on how to do this, I'm happy to help.

Thanks! 

—
Sincerely,

William Brown

Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux