From brian at shmoo.com Tue Feb 3 08:13:31 2004 From: brian at shmoo.com (Brian Wotring) Date: Tue, 3 Feb 2004 06:13:31 -0700 Subject: [osiris-devel] Osiris 3.0.2-current released Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Osiris version 3.0.2-current released - ----------------------------------------- Osiris - Host Integrity Monitoring http://osiris.shmoo.com This release of Osiris is primarily to address a bug with the configure script detecting lpthread. Downloads: http://osiris.shmoo.com/data/osiris-3.0.2-current.tar.gz http://osiris.shmoo.com/data/osiris-3.0.2-current-win32.exe Checksums and Signatures: MD5(osiris-3.0.2-current-win32.exe)= 6568a1f982f0b82bbff855368e9f3c6e MD5(osiris-3.0.2-current.tar.gz)= 6d6b9d019e95bf2e8ad73c1590981f6c http://osiris.shmoo.com/data/osiris-3.0.2-current.tar.gz.sig http://osiris.shmoo.com/data/osiris-3.0.2-current-win32.exe.sig Please forward any questions or comments to the Osiris mailing list: osiris at shmoo.com, and any questions related to development to the development list: osiris-devel at shmoo.com - -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 - not licensed for commercial use: www.pgp.com iQA/AwUBQB+eag3seZ6WdHY9EQKpdgCfRTDFFYR0Tel4nwSS7C/6vRQjYeQAoNKb YP3mRf9HJ1vE0MJmIGh9noe7 =3MW4 -----END PGP SIGNATURE----- From rdump at river.com Wed Feb 4 22:05:03 2004 From: rdump at river.com (Richard Johnson) Date: Wed, 4 Feb 2004 20:05:03 -0700 Subject: [osiris-devel] gnu regex current build problems on openbsd Message-ID: I'm seeing the following build failure on -current on OpenBSD i386 and sparc64 boxes, but not on Mac OX 10.3.2 (where it builds fine). I haven't looked at in greater detail beyond suspecting include issues -- I just backed out for now to test some local changes. | source='regex.c' object='regex.o' libtool=no depfile='.deps/regex.Po' | tmpdepfile='.deps/regex.TPo' depmode=gcc /bin/sh ../../depcomp gcc | -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/libfileapi -g -c `test -f | 'regex.c' || echo './'`regex.c | regex.c:2377: warning: data definition has no type or storage class | regex.c:2377: syntax error before `while' | *** Error code 1 | | Stop in /usr/local/src/osiris/src/libosiris. | *** Error code 1 | | Stop in /usr/local/src/osiris (line 440 of Makefile). Richard From brian at shmoo.com Wed Feb 4 23:19:13 2004 From: brian at shmoo.com (Brian Wotring) Date: Wed, 4 Feb 2004 21:19:13 -0700 Subject: [osiris-devel] gnu regex current build problems on openbsd In-Reply-To: References: Message-ID: <740AAB70-5792-11D8-B39B-000393578C14@shmoo.com> Hm...looks like a ^M slipped in at the end of line 2376. Try removing that. On Feb 4, 2004, at 8:05 PM, Richard Johnson wrote: > I'm seeing the following build failure on -current on OpenBSD i386 and > sparc64 boxes, but not on Mac OX 10.3.2 (where it builds fine). I > haven't looked at in greater detail beyond suspecting include issues -- > I just backed out for now to test some local changes. > > > | source='regex.c' object='regex.o' libtool=no > depfile='.deps/regex.Po' | > tmpdepfile='.deps/regex.TPo' depmode=gcc /bin/sh ../../depcomp gcc | > -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/libfileapi -g -c `test > -f | > 'regex.c' || echo './'`regex.c > | regex.c:2377: warning: data definition has no type or storage class > | regex.c:2377: syntax error before `while' > | *** Error code 1 > | > | Stop in /usr/local/src/osiris/src/libosiris. > | *** Error code 1 > | > | Stop in /usr/local/src/osiris (line 440 of Makefile). > > > Richard > _______________________________________________ > osiris-devel mailing list > osiris-devel at lists.shmoo.com > https://lists.shmoo.com/mailman/listinfo/osiris-devel > > -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D From brian at shmoo.com Mon Feb 9 08:35:50 2004 From: brian at shmoo.com (Brian Wotring) Date: Mon, 9 Feb 2004 06:35:50 -0700 Subject: [osiris-devel] Osiris 3.0.4-current released Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Osiris version 3.0.4-current released - ------------------------------------------ Osiris - Host Integrity Monitoring http://osiris.shmoo.com This release of Osiris-current contains support for monitoring kernel modules on Solaris. Downloads: http://osiris.shmoo.com/data/osiris-3.0.4-current.tar.gz http://osiris.shmoo.com/data/osiris-3.0.4-current-win32.exe Checksums and Signatures: MD5(osiris-3.0.4-current-win32.exe)= 6f76d23612a2b3712b4784cca976ff68 MD5(osiris-3.0.4-current.tar.gz)= 836b1c9495dc4538432a2c435c5d341f http://osiris.shmoo.com/data/osiris-3.0.4-current.tar.gz.sig http://osiris.shmoo.com/data/osiris-3.0.4-current-win32.exe.sig Please forward any questions or comments to the Osiris mailing list: osiris at shmoo.com, and any questions related to development to the development list: osiris-devel at shmoo.com - -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 - not licensed for commercial use: www.pgp.com iQA/AwUBQCeMpw3seZ6WdHY9EQKSvACggFpnNKFLNyoQYjE3QKSq4n2sw6UAniNx ZAR7ngNVO28ebaFA0Y+uX4XK =cq2w -----END PGP SIGNATURE----- From Alexei_Roudnev at exigengroup.com Wed Feb 18 18:06:06 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Wed, 18 Feb 2004 15:06:06 -0800 Subject: [osiris-devel] monitoring host state References: <123601c3d3c7$36c468a0$267f300a@exigengroup.com><002a01c3d495$20a892c0$870ea8c0@exigengroup.com><5C91061A-4089-11D8-BC01-000393578C14@shmoo.com><00f501c3d49f$72db9e70$870ea8c0@exigengroup.com> <72752864-4093-11D8-BC01-000393578C14@shmoo.com> Message-ID: <049401c3f673$ca5cd7e0$870ea8c0@exigengroup.com> Brian. What do you think, if we add 'system authentication' into the osiris? I mean - for WinNT, I can write out code, allowing to use NT user names / passwords instead of internal data base (so that you can configure 'require group xxx'); for Unix, you can use pam (at least, in theory). Now, I have some problems with access / authentication. One is _no system authentication allowed_, other _I can not restrict user to some hosts or some operations only_. This are minor problems, but they do exists. Alex > > checkout -r rel_3_dev > > On Jan 6, 2004, at 2:52 PM, Alexei Roudnev wrote: > > > Hmm, NT.. I think I have (yet) 1 NT. I'll try to verify (btw, virtusl > > machines can be a good choice for testing). > > > > Which version - 3.0? > > > > ----- Original Message ----- > > From: "Brian Wotring" > > To: "Osiris Developers" > > Sent: Tuesday, January 06, 2004 12:46 PM > > Subject: Re: [osiris-devel] monitoring host state > > > > > >> > >> I've only tested this on Windows 2000. If you could verify this on NT > >> and XP, that would be really helpful. > >> > >> On Jan 6, 2004, at 1:39 PM, Alexei Roudnev wrote: > >> > >>> Excellent - if it works -:). > >>> > >>> Where (which OS) did you tested it already? > >>> > >>> ----- Original Message ----- > >>> From: "Brian Wotring" > >>> To: "Osiris Developers" > >>> Sent: Tuesday, January 06, 2004 6:02 AM > >>> Subject: Re: [osiris-devel] monitoring host state > >>> > >>> > >>>> > >>>> The user entry for Windows now contains a list of groups that user > >>>> is > >>>> a > >>>> member of. > >>>> > >>>> On Jan 5, 2004, at 1:05 PM, Alexei_Roudnev wrote: > >>>> > >>>>> For Windows, you need to monitor, at least, > >>>>> > >>>>> Users, 'Member Of', with names insted of group SID. I can find a > >>>>> code, > >>>>> which allowed to extract such information (I wrote it in past - > >>>>> user, > >>>>> list > >>>>> of groups). > >>>>> > >>>>> It is not excellent, but works. > >>>>> > >>>>> > >>>>> ----- Original Message ----- > >>>>> From: "Brian Wotring" > >>>>> To: "Osiris Developers" > >>>>> Sent: Monday, January 05, 2004 11:38 AM > >>>>> Subject: [osiris-devel] monitoring host state > >>>>> > >>>>> > >>>>>> > >>>>>> Here is what we have so far. I'm mostly concerned with the lack > >>>>>> of > >>>>>> any > >>>>>> significant attributes on the Windows side. If anyone knows of > >>>>>> any > >>>>>> way > >>>>>> to expand this, now is the time. > >>>>>> > >>>>>> unix users: name,uid,gid,gecos,home,shell > >>>>>> windows users: name, privs, home, flags, auth_flags > >>>>>> > >>>>>> unix groups: group,gid > >>>>>> > >>>>>> For Windows, only the name. The LOCAL_GROUP_INFO structure > >>>>>> contains > >>>>>> only the name and the comment field. Getting the gid and other > >>>>>> attributes requires using NetGroupEnum(), which I have found to be > >>>>>> unreliable for listing local group information. > >>>>>> > >>>>>> linux kmods: same as output from lsmod > >>>>>> darwin kexts: same as output from kextstat > >>>>>> windows kmods (services): name, display_name, status (types > >>>>>> SERVICE_WIN32) > >>>>>> > >>>>>> -- > >>>>>> Brian Wotring ( brian at shmoo.com ) > >>>>>> PGP KeyID: 0x9674763D > >>>>>> > >>>>>> _______________________________________________ > >>>>>> osiris-devel mailing list > >>>>>> osiris-devel at lists.shmoo.com > >>>>>> https://lists.shmoo.com/mailman/listinfo/osiris-devel > >>>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> osiris-devel mailing list > >>>>> osiris-devel at lists.shmoo.com > >>>>> https://lists.shmoo.com/mailman/listinfo/osiris-devel > >>>>> > >>>>> > >>>> -- > >>>> Brian Wotring ( brian at shmoo.com ) > >>>> PGP KeyID: 0x9674763D > >>>> > >>>> _______________________________________________ > >>>> osiris-devel mailing list > >>>> osiris-devel at lists.shmoo.com > >>>> https://lists.shmoo.com/mailman/listinfo/osiris-devel > >>>> > >>> _______________________________________________ > >>> osiris-devel mailing list > >>> osiris-devel at lists.shmoo.com > >>> https://lists.shmoo.com/mailman/listinfo/osiris-devel > >>> > >>> > >> -- > >> Brian Wotring ( brian at shmoo.com ) > >> PGP KeyID: 0x9674763D > >> > >> _______________________________________________ > >> osiris-devel mailing list > >> osiris-devel at lists.shmoo.com > >> https://lists.shmoo.com/mailman/listinfo/osiris-devel > >> > > > > _______________________________________________ > > osiris-devel mailing list > > osiris-devel at lists.shmoo.com > > https://lists.shmoo.com/mailman/listinfo/osiris-devel > > > > > -- > Brian Wotring ( brian at shmoo.com ) > PGP KeyID: 0x9674763D > > _______________________________________________ > osiris-devel mailing list > osiris-devel at lists.shmoo.com > https://lists.shmoo.com/mailman/listinfo/osiris-devel > From luke at responsys.com Fri Feb 20 08:01:38 2004 From: luke at responsys.com (Luke West) Date: Fri, 20 Feb 2004 05:01:38 -0800 Subject: [osiris-devel] Typo in web page authentication Message-ID: <3DD86CAAF0AFD211A88400508B8B3B530A8396B9@ex-pa-u1.us.responsys.com> Brian, Minor typographic error in the web page authentication :- "Alternatively, you can login to the mangement console and update the database manually." Management is spelt wrongly. L. Luke West From thomas.jones at linux-howtos.com Thu Feb 19 23:51:37 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Thu, 19 Feb 2004 22:51:37 -0600 Subject: [osiris-devel] Typo in web page authentication In-Reply-To: <3DD86CAAF0AFD211A88400508B8B3B530A8396B9@ex-pa-u1.us.responsys.com> References: <3DD86CAAF0AFD211A88400508B8B3B530A8396B9@ex-pa-u1.us.responsys.com> Message-ID: <200402192251.46108.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 20 February 2004 07:01, Luke West wrote: > Brian, > > Minor typographic error in the web page authentication :- > > "Alternatively, you can login to the mangement console and update the > database manually." > > Management is spelt wrongly. > > L. > Luke West > _______________________________________________ > osiris-devel mailing list > osiris-devel at lists.shmoo.com > https://lists.shmoo.com/mailman/listinfo/osiris-devel There were various mispellings throughout the source code. Most have been noted. I have been scouring the sources to find most all of these; to include the example as stated by yourself. I hope to forward the diff'd results to the core developers before the next release. ;) Thanks. Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFANZJfQT2komo99ukRAk1wAJ9bUXfITd8zZY4BYYvVlXmgiYLLMACgieOH yOuG/IAlMgVYGgy+wisaP+I= =O9Xf -----END PGP SIGNATURE----- From thomas.jones at linux-howtos.com Sat Feb 21 17:13:18 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Sat, 21 Feb 2004 16:13:18 -0600 Subject: [osiris-devel] 3.0.4-current development documentation? Message-ID: <200402211613.25080.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, Has someone already generated the proper documentation for the Osiris system development? I didn't notice it on the website; so I went ahead and generated the appropriate documentation in the following formats: - - html - - latex - - xml - - pdf Does anyone want a copy of these? BTW.....I changed the comment structure of all struct's to the JavaDoc specification. Is this a problem, Brian? It would be alot more efficient to change the source headers so as to be easily recognizable during generation. Is that ok? Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAN9gDQT2komo99ukRAlmsAKDKLG3cMZmJvRzuk8Raa+Fwj9scvwCfYqZy LchVquyal7wEL3HWurPebWg= =hG6T -----END PGP SIGNATURE----- From Alexei_Roudnev at exigengroup.com Sun Feb 22 15:02:30 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Sun, 22 Feb 2004 12:02:30 -0800 Subject: [osiris-devel] 3.0.4-current development documentation? References: <200402211613.25080.thomas.jones@linux-howtos.com> Message-ID: <06ef01c3f97e$cdcf8270$870ea8c0@exigengroup.com> Who need documentation in so many formats? html + pdf is quite good combination. PS. I used 'doxigen' to generate API documentation (analog of JavaDoc), but remember, that it is not enough just to document system calls etc - we _ALWAYS_ created a few special _Doxigen only_ files to maintain big documents, indexes and so on. And - do not use such things to generate user's documentation, but generate reference manuals only. Alex ----- Original Message ----- From: "Thomas Jones" To: "Osiris Developers" Sent: Saturday, February 21, 2004 2:13 PM Subject: [osiris-devel] 3.0.4-current development documentation? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello all, Has someone already generated the proper documentation for the Osiris system development? I didn't notice it on the website; so I went ahead and generated the appropriate documentation in the following formats: - - html - - latex - - xml - - pdf Does anyone want a copy of these? BTW.....I changed the comment structure of all struct's to the JavaDoc specification. Is this a problem, Brian? It would be alot more efficient to change the source headers so as to be easily recognizable during generation. Is that ok? Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAN9gDQT2komo99ukRAlmsAKDKLG3cMZmJvRzuk8Raa+Fwj9scvwCfYqZy LchVquyal7wEL3HWurPebWg= =hG6T -----END PGP SIGNATURE----- _______________________________________________ osiris-devel mailing list osiris-devel at lists.shmoo.com https://lists.shmoo.com/mailman/listinfo/osiris-devel From thomas.jones at linux-howtos.com Sun Feb 22 04:03:17 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Sun, 22 Feb 2004 03:03:17 -0600 Subject: [osiris-devel] 3.0.4-current development documentation? In-Reply-To: <06ef01c3f97e$cdcf8270$870ea8c0@exigengroup.com> References: <200402211613.25080.thomas.jones@linux-howtos.com> <06ef01c3f97e$cdcf8270$870ea8c0@exigengroup.com> Message-ID: <200402220303.22810.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 14:02, Alexei Roudnev wrote: > Who need documentation in so many formats? html + pdf is quite good > combination. > > PS. I used 'doxigen' to generate API documentation (analog of JavaDoc), but > remember, that it is not enough just to document system calls etc - we > _ALWAYS_ created a few special _Doxigen only_ files to maintain big > documents, indexes and so on. > > And - do not use such things to generate user's documentation, but generate > reference manuals only. > > Alex Geez O'pete !!!! You are killing me. XML is easily extensible to almost any other format with a standard DTD. AND can be utilized and referenced with readbility formulas(Dale-Chall, Flesch) so that even general user documentation can be compiled very quickly. i.e. KDE document sourcing, etc..... As for LaTeX ----- is very easy to transform this format to desktop reference materials, for various different platforms. Given that Osiris is not system dependant; this makes very good sense. BTW --- doxygen "only" files are redundant. It would be considerably easier to just correctly format the comments directly into the sources. Why comment source code to make it incompatible with doxygen, then make another file for the same data that is compiled by said document. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOHBZQT2komo99ukRAmNdAKCM7VkhSvrBNkI+/E7MZtq2YTY08ACgvwYI 9XDt+0aaIZr/keNomxrnrqg= =dMhp -----END PGP SIGNATURE----- From Alexei_Roudnev at exigengroup.com Sun Feb 22 16:39:11 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Sun, 22 Feb 2004 13:39:11 -0800 Subject: [osiris-devel] 3.0.4-current development documentation? References: <200402211613.25080.thomas.jones@linux-howtos.com><06ef01c3f97e$cdcf8270$870ea8c0@exigengroup.com> <200402220303.22810.thomas.jones@linux-howtos.com> Message-ID: <072301c3f98c$4f44c330$870ea8c0@exigengroup.com> Sorry, Tom. Of course, it is not a bad idea, and it is only a _disk space_ issue. But remember, that 99% of all users do not need your xml, dtd etc - they need plain text on the screen, so pdf file or html file looks quite enough for the _binary_ distribution. Anyway, it's not important, I have not any objections. Doxigen (JavaDoc etc) is quite another issue. In real projects, it is not _redundant_. Reason is very simple: - documentation is edited and corrected by _technical editor_, _technical corrector_ etc; - you do not want them to edit a sources; - you do not want to have a include file, having 90% of the documentation and 10% of the source code. But, on the other hand, you want to write documentation in such style, that it is auto-referenced - if I write out API call, I'd like to see html link on this place, not a plain text. As a result, after a few experiments, we added special suffix, .dxf, to the list of source files, and moved all _BIG_ pieces of documentation into it. For example, if we have some subsystem, we put subsystem description, with a simple usage example, here, and enlist all API interfaces in the end. Remember, that user is not looking for the 'CLASS' or 'ABC::xxx' function; he is looking for, for example, 'How can I create, maintain and delete a thread and set/unset mutex, when I use this system'. It is very important. Documentation have a 3 file types - - plain html documents, used as a index-I level; - dxf files, working as an introduction to the subsystems, servers, config files etc, and used as a index-II level; - .cpp and .h files, used to generate detailed references to the api functions. It worked fine. I saw the same approach in a few other projects (QT, for example) - do not say _I have a doxigen and it provides a documentation_ (because it provides a garbage) but say _I have a documentation, and I use doxigen to document functions and classes, so I am 100% sure than they are documented up-to-date, and I use dxf files for other documentation, so they are processed by technical editor and corrector, are written in free-lance style, do not create a mess in include directories, and uses doxigen class and method description for detailed references_. Just again - Doxigen or JavaDoc provides, by themself, a mess of 90% useless reference manuals. Here is an example (I used abandoned project. btw - EOL project is abandoned, but exists and in working conditions, if someone is interested in multi-platform middleware, we can try to put life into it). Level I document - plain html: -------------------------------------------------------------------------------- Exigen Middleware: Exigen Object Library (EOL) Documentation Release Notes. -------------------------------------------------------------------------------- 1. Quick Start Introduction and functional overview EOL Security design EOL Cookbook a.. Sample Chat Application: Introduction b.. Client EODL mapping and implementation c.. Server EODL mapping and implementation d.. Object Lifecycle Usage e.. Creating evolving designs: multiple versions of the simple chat application -------------------------------------------------------------------------------- 2. EOL User's Guide a.. EOL Naming Service User's Guide b.. Dynamic type usage c.. EIO Introduction and MT Guide d.. ELS User's Guide e.. ETP User's Guide -------------------------------------------------------------------------------- Level 2 document - .dxf file. Main Page Modules Namespace List Class Hierarchy Alphabetical List Compound List File List Namespace Members Compound Members File Members Related Pages -------------------------------------------------------------------------------- EOL Naming Service : User's Guide Introduction EOL Objects can be of two types: a.. well known - with well known object references which can be written out before object is running; b.. normal - which contains signature based on the random seed and must be registered before any client can subscribe to them. Naming service provides: a.. registration (named 'binding') of the server objects; b.. resolution of the objects by their names; c.. basic access control; d.. basic redundancy for the objects. EOL Naming Service API Usually programs should not bother about naming service and work with Name Service directly, but should use EOL Naming Service API instead. This API allows: a.. Register server object by its name (EOLServerObject::makeBinding()) for the full or restricted access. Server object can be registered a few times with the different names and different access rights, and can be unregistered as well. A few servers can register objects with the same names that allows to set up redundant configurations. b.. Subscribe to the object by its name (in synchronous or asynchronous mode). If a few servers were registered, subscription will choose the nearest server and skip servers that do not answer. c.. Use ENSNameContext, EOLStaticNameContext, EOLResolver and EOLBinding classes for more specific tasks. -------------------------------------------------------------------------------- ================= Geez O'pete !!!! You are killing me. XML is easily extensible to almost any other format with a standard DTD. AND can be utilized and referenced with readbility formulas(Dale-Chall, Flesch) so that even general user documentation can be compiled very quickly. i.e. KDE document sourcing, etc..... As for LaTeX ----- is very easy to transform this format to desktop reference materials, for various different platforms. Given that Osiris is not system dependant; this makes very good sense. BTW --- doxygen "only" files are redundant. It would be considerably easier to just correctly format the comments directly into the sources. Why comment source code to make it incompatible with doxygen, then make another file for the same data that is compiled by said document. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOHBZQT2komo99ukRAmNdAKCM7VkhSvrBNkI+/E7MZtq2YTY08ACgvwYI 9XDt+0aaIZr/keNomxrnrqg= =dMhp -----END PGP SIGNATURE----- _______________________________________________ osiris-devel mailing list osiris-devel at lists.shmoo.com https://lists.shmoo.com/mailman/listinfo/osiris-devel -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.shmoo.com/pipermail/osiris-devel/attachments/20040222/31084f82/attachment.htm From thomas.jones at linux-howtos.com Sun Feb 22 05:30:26 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Sun, 22 Feb 2004 04:30:26 -0600 Subject: [osiris-devel] 3.0.4-current development documentation? In-Reply-To: <072301c3f98c$4f44c330$870ea8c0@exigengroup.com> References: <200402211613.25080.thomas.jones@linux-howtos.com> <200402220303.22810.thomas.jones@linux-howtos.com> <072301c3f98c$4f44c330$870ea8c0@exigengroup.com> Message-ID: <200402220430.32956.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 15:39, Alexei Roudnev wrote: > Sorry, Tom. Of course, it is not a bad idea, and it is only a _disk space_ > issue. > > But remember, that 99% of all users do not need your xml, dtd etc - they > need plain text on the screen, so pdf file or html file looks quite enough > for the _binary_ distribution. Anyway, it's not important, I have not any > objections. > > Doxigen (JavaDoc etc) is quite another issue. In real projects, it is not > _redundant_. Reason is very simple: - documentation is edited and corrected > by _technical editor_, _technical corrector_ etc; - you do not want them to > edit a sources; > - you do not want to have a include file, having 90% of the documentation > and 10% of the source code. > I am a Technical Education Specialist for a Fortune 500 company ----- I am pretty sure that i understand the theory behind technical documentation procedures and/or processes. If you had noticed, I made the comment that the core developers utilize JavaDoc. This was not posted to the User List. Thus, it is a generally accepted as a reasonable request for technical individuals. I think you may be getting the standard documentation procedures confused and/ or integrated with your backward way of processing data. The whole process you ranted about is simply useless. You again are highly confused; and elaborate exceedingly about irrational ways to perform various procedures. Even though they(standard procedures) are widely accepted by the developemnt community. Here are a couple example highlights: - But remember, that 99% of all users do not need your xml This is a development reference, on a development list. Enough said. - - .cpp and .h files, used to generate detailed references to the api functions. Doesn't ALL documentation "generator's"; utilize the same files as above? - - a mess of ?90% useless reference manuals Any documentation that applies to the referenced material is not useless. It may very well be beyond the scope of your knowledge; but to other more advanced developers it is very efficient. Rather than providing your unorthodox ways of performing various procedures; it would considerably easier if you were to just make contributions to the project in the areas that you feel you are exceedingly qualified. Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOITHQT2komo99ukRAjYNAJ41d7K0QyXsOPWHoygYw0q2GjrOuACgoSXf sCAARaScWFNNIpip+k0gBXM= =N5HH -----END PGP SIGNATURE----- From brian at shmoo.com Sun Feb 22 17:28:34 2004 From: brian at shmoo.com (Brian Wotring) Date: Sun, 22 Feb 2004 14:28:34 -0800 Subject: [osiris-devel] 3.0.4-current development documentation? In-Reply-To: <200402211613.25080.thomas.jones@linux-howtos.com> References: <200402211613.25080.thomas.jones@linux-howtos.com> Message-ID: <735F4352-6586-11D8-959B-000393578C14@shmoo.com> On Feb 21, 2004, at 2:13 PM, Thomas Jones wrote: > Has someone already generated the proper documentation for the Osiris > system > development? Not to my knowledge, no. > I didn't notice it on the website; so I went ahead and generated the > appropriate documentation in the following formats: > > - - html > - - latex > - - xml > - - pdf > > Does anyone want a copy of these? BTW.....I changed the comment > structure of > all struct's to the JavaDoc specification. Is this a problem, Brian? > It would > be alot more efficient to change the source headers so as to be easily > recognizable during generation. Is that ok? Yes, this is fine. I have no problem with doing this. -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D From Alexei_Roudnev at exigengroup.com Sun Feb 22 17:55:30 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Sun, 22 Feb 2004 14:55:30 -0800 Subject: [osiris-devel] 3.0.4-current development documentation? References: <200402211613.25080.thomas.jones@linux-howtos.com><200402220303.22810.thomas.jones@linux-howtos.com><072301c3f98c$4f44c330$870ea8c0@exigengroup.com> <200402220430.32956.thomas.jones@linux-howtos.com> Message-ID: <074301c3f996$f8fdd060$870ea8c0@exigengroup.com> Thomas; I did not proposed to help with documentation _only_ because English is not my native language. I wrote a huge amount of technical documentation in my life. So, I have some background for my opinion (as I was saying, I do not insist about xml etc, through it's importance is overestimated). If you open any _good_ project, such as QT, you will see the same approach - documentation files are part of the project (cvs-ed etc) but are separated, on level 1 and level-2, from the source files. level-3 (function XXX, parameters, return, short description) is kept inside source files. If you are intending, that Sun (who uses JavaDoc approach) provides _GOOD_ documentation, then I am very sorry. Alex ----- Original Message ----- From: "Thomas Jones" To: Sent: Sunday, February 22, 2004 2:30 AM Subject: Re: [osiris-devel] 3.0.4-current development documentation? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 15:39, Alexei Roudnev wrote: > Sorry, Tom. Of course, it is not a bad idea, and it is only a _disk space_ > issue. > > But remember, that 99% of all users do not need your xml, dtd etc - they > need plain text on the screen, so pdf file or html file looks quite enough > for the _binary_ distribution. Anyway, it's not important, I have not any > objections. > > Doxigen (JavaDoc etc) is quite another issue. In real projects, it is not > _redundant_. Reason is very simple: - documentation is edited and corrected > by _technical editor_, _technical corrector_ etc; - you do not want them to > edit a sources; > - you do not want to have a include file, having 90% of the documentation > and 10% of the source code. > I am a Technical Education Specialist for a Fortune 500 company ----- I am pretty sure that i understand the theory behind technical documentation procedures and/or processes. If you had noticed, I made the comment that the core developers utilize JavaDoc. This was not posted to the User List. Thus, it is a generally accepted as a reasonable request for technical individuals. I think you may be getting the standard documentation procedures confused and/ or integrated with your backward way of processing data. The whole process you ranted about is simply useless. You again are highly confused; and elaborate exceedingly about irrational ways to perform various procedures. Even though they(standard procedures) are widely accepted by the developemnt community. Here are a couple example highlights: - But remember, that 99% of all users do not need your xml This is a development reference, on a development list. Enough said. - - .cpp and .h files, used to generate detailed references to the api functions. Doesn't ALL documentation "generator's"; utilize the same files as above? - - a mess of 90% useless reference manuals Any documentation that applies to the referenced material is not useless. It may very well be beyond the scope of your knowledge; but to other more advanced developers it is very efficient. Rather than providing your unorthodox ways of performing various procedures; it would considerably easier if you were to just make contributions to the project in the areas that you feel you are exceedingly qualified. Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOITHQT2komo99ukRAjYNAJ41d7K0QyXsOPWHoygYw0q2GjrOuACgoSXf sCAARaScWFNNIpip+k0gBXM= =N5HH -----END PGP SIGNATURE----- _______________________________________________ osiris-devel mailing list osiris-devel at lists.shmoo.com https://lists.shmoo.com/mailman/listinfo/osiris-devel From Alexei_Roudnev at exigengroup.com Sun Feb 22 18:00:26 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Sun, 22 Feb 2004 15:00:26 -0800 Subject: [osiris-devel] 3.0.4-current development documentation? References: <200402211613.25080.thomas.jones@linux-howtos.com> <735F4352-6586-11D8-959B-000393578C14@shmoo.com> Message-ID: <074f01c3f997$a91a31f0$870ea8c0@exigengroup.com> Btw - sorry, if I was not understanding - I have not any, even minimal, complain about it. (And it is Brian who makes a decision, anyway). I'd like just to prevent the case, when, instead of good technical document we have a lot of JavaDoc generated documents, which are pretty correct and pretty useless without something, linking them together and explaining, how it all works. I saw many such projects, and I do not want to see osiris going intpo the same blackhole... Alex PS. Fortune-500 company means nothing except huge burocrasy. ----- Original Message ----- From: "Brian Wotring" To: "Osiris Developers" Sent: Sunday, February 22, 2004 2:28 PM Subject: Re: [osiris-devel] 3.0.4-current development documentation? > > On Feb 21, 2004, at 2:13 PM, Thomas Jones wrote: > > > Has someone already generated the proper documentation for the Osiris > > system > > development? > > Not to my knowledge, no. > > > I didn't notice it on the website; so I went ahead and generated the > > appropriate documentation in the following formats: > > > > - - html > > - - latex > > - - xml > > - - pdf > > > > Does anyone want a copy of these? BTW.....I changed the comment > > structure of > > all struct's to the JavaDoc specification. Is this a problem, Brian? > > It would > > be alot more efficient to change the source headers so as to be easily > > recognizable during generation. Is that ok? > > Yes, this is fine. I have no problem with doing this. > > -- > Brian Wotring ( brian at shmoo.com ) > PGP KeyID: 0x9674763D > > _______________________________________________ > osiris-devel mailing list > osiris-devel at lists.shmoo.com > https://lists.shmoo.com/mailman/listinfo/osiris-devel > From thomas.jones at linux-howtos.com Sun Feb 22 06:10:19 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Sun, 22 Feb 2004 05:10:19 -0600 Subject: [osiris-devel] 3.0.4-current development documentation? In-Reply-To: <074301c3f996$f8fdd060$870ea8c0@exigengroup.com> References: <200402211613.25080.thomas.jones@linux-howtos.com> <200402220430.32956.thomas.jones@linux-howtos.com> <074301c3f996$f8fdd060$870ea8c0@exigengroup.com> Message-ID: <200402220510.37311.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 16:55, Alexei Roudnev wrote: > Thomas; I did not proposed to help with documentation _only_ because > English is not my native language. I wrote a huge amount of technical > documentation in my life. So, I have some background for my opinion (as I > was saying, I do not insist about xml etc, through it's importance is > overestimated). > > If you open any _good_ project, such as QT, you will see the same approach > - documentation files are part of the project (cvs-ed etc) but are > separated, on level 1 and level-2, from the source files. level-3 (function > XXX, parameters, return, short description) is kept inside source files. > > If you are intending, that Sun (who uses JavaDoc approach) provides _GOOD_ > documentation, then I am very sorry. > > Alex It is obvious that you make no intention to provide any valid contribution to this community. Other than those being negative in context. Regrettably, you leave me no choice; you have been killfile'd. Good Luck! Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAOI4fQT2komo99ukRAs6uAKC513ICWEgr5EXjr7Oj0NB1ArGE0QCgl5gG JfwBeuKqqQLg5VSMDl98oWo= =AuEA -----END PGP SIGNATURE----- From thomas.jones at linux-howtos.com Sun Feb 22 11:59:33 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Sun, 22 Feb 2004 10:59:33 -0600 Subject: [osiris-devel] SuSE 9.0 RPM Available Message-ID: <200402221059.52434.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK all, I have made it to the beta phase of "osirismd-3.0.4-current.i586.rpm". I have a little debugging to do for the post-installation scripts to remove the generated start/stop RC*.d links. But all else seems to be working great. If anyone here is using a SuSE system; please email me and i'll forward this to you for testing. Brian, i've finally got it close!!!! ;) Notes: - All preemptive installation procedures are scripted within. - adding group - adding user - generating next sequential initialization scripts (S & K) - S & K scripts no longer static numbers - There is a .version number generated during installation for debugging - A congratulatory note has been constructed for every installation - Uninstall removes all changes made from %pre section Todo: - Fix postinstall S & K removal - Add-in SuSEconfig call upon post-installation - This will reload init - Also will forward the congratulatory note to the root at localhost email account - Will also place a Update Message link to /var/log/update-messages on the user's Desktop - Verify that the rpm conforms to Linux Standard Base 1.3 Hello, Congratulations on the successful installation of the Osiris Host Integrity System. Your next steps should include: [ Configuration } Stuff here! [ Services] Stuff here! [ Documentation ] Stuff here! Have fun! The Shmoo group, http://osiris.shmoo.com I need some feedback on the content of the message. I think it is a good idea to include URL links to local documentation. And possibly a step-by-step how-to on how to generate/start-up the daemon. If this is generally accepted, it will be considerably easier to construct the osirisd rpm. ;) Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAON/7QT2komo99ukRAsbOAJ9TN8eCQoOGX7iVgEgS6rFNnWpB+ACfVsHH MRo7LmUYvt/Zx0fNcl6yyz4= =Qbr7 -----END PGP SIGNATURE----- From Alexei_Roudnev at exigengroup.com Mon Feb 23 00:18:36 2004 From: Alexei_Roudnev at exigengroup.com (Alexei Roudnev) Date: Sun, 22 Feb 2004 21:18:36 -0800 Subject: [osiris-devel] SuSE 9.0 RPM Available References: <200402221059.52434.thomas.jones@linux-howtos.com> Message-ID: <075901c3f9cc$7d6dac50$870ea8c0@exigengroup.com> I have SuSe in the lab. ----- Original Message ----- From: "Thomas Jones" To: "Osiris Developers" Sent: Sunday, February 22, 2004 8:59 AM Subject: [osiris-devel] SuSE 9.0 RPM Available -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK all, I have made it to the beta phase of "osirismd-3.0.4-current.i586.rpm". I have a little debugging to do for the post-installation scripts to remove the generated start/stop RC*.d links. But all else seems to be working great. If anyone here is using a SuSE system; please email me and i'll forward this to you for testing. Brian, i've finally got it close!!!! ;) Notes: - All preemptive installation procedures are scripted within. - adding group - adding user - generating next sequential initialization scripts (S & K) - S & K scripts no longer static numbers - There is a .version number generated during installation for debugging - A congratulatory note has been constructed for every installation - Uninstall removes all changes made from %pre section Todo: - Fix postinstall S & K removal - Add-in SuSEconfig call upon post-installation - This will reload init - Also will forward the congratulatory note to the root at localhost email account - Will also place a Update Message link to /var/log/update-messages on the user's Desktop - Verify that the rpm conforms to Linux Standard Base 1.3 Hello, Congratulations on the successful installation of the Osiris Host Integrity System. Your next steps should include: [ Configuration } Stuff here! [ Services] Stuff here! [ Documentation ] Stuff here! Have fun! The Shmoo group, http://osiris.shmoo.com I need some feedback on the content of the message. I think it is a good idea to include URL links to local documentation. And possibly a step-by-step how-to on how to generate/start-up the daemon. If this is generally accepted, it will be considerably easier to construct the osirisd rpm. ;) Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAON/7QT2komo99ukRAsbOAJ9TN8eCQoOGX7iVgEgS6rFNnWpB+ACfVsHH MRo7LmUYvt/Zx0fNcl6yyz4= =Qbr7 -----END PGP SIGNATURE----- _______________________________________________ osiris-devel mailing list osiris-devel at lists.shmoo.com https://lists.shmoo.com/mailman/listinfo/osiris-devel From thomas.jones at linux-howtos.com Mon Feb 23 14:10:42 2004 From: thomas.jones at linux-howtos.com (Thomas Jones) Date: Mon, 23 Feb 2004 13:10:42 -0600 Subject: [osiris-devel] SuSE 9.0 RPM Available In-Reply-To: <200402221059.52434.thomas.jones@linux-howtos.com> References: <200402221059.52434.thomas.jones@linux-howtos.com> Message-ID: <200402231311.07826.thomas.jones@linux-howtos.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 10:59, Thomas Jones wrote: > OK all, > > I have made it to the beta phase of "osirismd-3.0.4-current.i586.rpm". > > I have a little debugging to do for the post-installation scripts to remove > the generated start/stop RC*.d links. But all else seems to be working > great. > > If anyone here is using a SuSE system; please email me and i'll forward > this to you for testing. Brian, i've finally got it close!!!! ;) > > Notes: > > - All preemptive installation procedures are scripted within. > - adding group > - adding user > - generating next sequential initialization scripts (S & K) > - S & K scripts no longer static numbers > - There is a .version number generated during installation for debugging > - A congratulatory note has been constructed for every installation > - Uninstall removes all changes made from %pre section > > Todo: > > - Fix postinstall S & K removal > - Add-in SuSEconfig call upon post-installation > - This will reload init > - Also will forward the congratulatory note to the root at localhost email > account > - Will also place a Update Message link to /var/log/update-messages on > the user's Desktop > - Verify that the rpm conforms to Linux Standard Base 1.3 > Update! Replaced chkconfig function in %pre scriptlet with LSB compliant functions: install_initd and remove_initd. Fixes S & K rc link problem. SuSEconfig is now called. This is called directly from the %post script so ALL stdout is directed to the user's shell(in both shell and kpackage processes). Up-side ---- this provides user with an account of what actually is going on with the system. Instead of just processing blindly. Packages are now digitally signed using GPG. I utilized my own package signing key. However, numerous other keys may also sign on top of mine ------ hint-hint ----- core developers. I still need input on the congratulatory note!!!! Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: 'Thomas Jones Package Signing Key' iD8DBQFAOlA4QT2komo99ukRAimfAJ4sDPtq8ucHVd60hDeIkanRhUqKHACbBWK9 aOJR12u5TTFdKjc9ucMUec8= =YEd4 -----END PGP SIGNATURE----- From Alexei_Roudnev at exigengroup.com Tue Feb 24 14:07:24 2004 From: Alexei_Roudnev at exigengroup.com (Alexei_Roudnev) Date: Tue, 24 Feb 2004 11:07:24 -0800 Subject: [osiris-devel] SuSE 9.0 RPM Available References: <200402221059.52434.thomas.jones@linux-howtos.com> <200402231311.07826.thomas.jones@linux-howtos.com> Message-ID: <035901c3fb09$6f93f1f0$2c7f300a@sjc.exigengroup.com> I still did not received this package. ----- Original Message ----- From: "Thomas Jones" To: Sent: Monday, February 23, 2004 11:10 AM Subject: Re: [osiris-devel] SuSE 9.0 RPM Available -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 22 February 2004 10:59, Thomas Jones wrote: > OK all, > > I have made it to the beta phase of "osirismd-3.0.4-current.i586.rpm". > > I have a little debugging to do for the post-installation scripts to remove > the generated start/stop RC*.d links. But all else seems to be working > great. > > If anyone here is using a SuSE system; please email me and i'll forward > this to you for testing. Brian, i've finally got it close!!!! ;) > > Notes: > > - All preemptive installation procedures are scripted within. > - adding group > - adding user > - generating next sequential initialization scripts (S & K) > - S & K scripts no longer static numbers > - There is a .version number generated during installation for debugging > - A congratulatory note has been constructed for every installation > - Uninstall removes all changes made from %pre section > > Todo: > > - Fix postinstall S & K removal > - Add-in SuSEconfig call upon post-installation > - This will reload init > - Also will forward the congratulatory note to the root at localhost email > account > - Will also place a Update Message link to /var/log/update-messages on > the user's Desktop > - Verify that the rpm conforms to Linux Standard Base 1.3 > Update! Replaced chkconfig function in %pre scriptlet with LSB compliant functions: install_initd and remove_initd. Fixes S & K rc link problem. SuSEconfig is now called. This is called directly from the %post script so ALL stdout is directed to the user's shell(in both shell and kpackage processes). Up-side ---- this provides user with an account of what actually is going on with the system. Instead of just processing blindly. Packages are now digitally signed using GPG. I utilized my own package signing key. However, numerous other keys may also sign on top of mine ------ hint-hint ----- core developers. I still need input on the congratulatory note!!!! Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) Comment: 'Thomas Jones Package Signing Key' iD8DBQFAOlA4QT2komo99ukRAimfAJ4sDPtq8ucHVd60hDeIkanRhUqKHACbBWK9 aOJR12u5TTFdKjc9ucMUec8= =YEd4 -----END PGP SIGNATURE----- _______________________________________________ osiris-devel mailing list osiris-devel at lists.shmoo.com https://lists.shmoo.com/mailman/listinfo/osiris-devel From brian at shmoo.com Tue Feb 24 15:27:55 2004 From: brian at shmoo.com (Brian Wotring) Date: Tue, 24 Feb 2004 13:27:55 -0700 Subject: [osiris-devel] SuSE 9.0 RPM Available In-Reply-To: <200402221059.52434.thomas.jones@linux-howtos.com> References: <200402221059.52434.thomas.jones@linux-howtos.com> Message-ID: This should be sufficient, if you are looking for something more in-depth, let me know and we can add some more information to each section. Note, I would recommend putting the services part before configuration as it's necessary to start the services before configuring the management console. On Feb 22, 2004, at 9:59 AM, Thomas Jones wrote: > > Hello, > > Congratulations on the successful installation of the Osiris Host > Integrity > System. Your next steps should include: > > [ Configuration ] 1. Login to the management console and set the admin password. By default, connections are restricted to localhost, and the admin account does not have a password. Use the 'passwd' command to set the password for the admin account. 2. Configure the management console settings. Use the 'edit-mhost' command to start the configuration wizard. As part of the configuration, you will be prompted for a list of hosts/IPs that will be allowed to connect to this management console. > [ Services] To start the osiris management console, run the installed startup script as any user: /usr/sbin/rcosirismd To start the osiris scan agent, run the following command as root: /usr/sbin/rcosirisd > [ Documentation ] Online user documentation is available here: PDF: http://osiris.shmoo.com/docs/OsirisUserGuide-3.0.0.pdf HTML: http://osiris.shmoo.com/docs/html/OsirisUserGuide.html In addition, there is built-in help to the osiris command line interface, use the 'help' command. -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D From brian at shmoo.com Sat Feb 28 13:40:56 2004 From: brian at shmoo.com (Brian Wotring) Date: Sat, 28 Feb 2004 11:40:56 -0700 Subject: [osiris-devel] osiris 2.4.5-rc1 released Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Osiris version 2.4.5-rc1 released - ------------------------------------------- Osiris - Host Integrity Monitoring http://osiris.shmoo.com This candidate release of Osiris contains no new features, and the following fixes: - - all of the -Wall warnings have finally been addressed. - - Berkeley DB truncation not working as expected, db files were bigger than necessary on overwrite's (not archiving). This has been fixed. The db truncation routines will be put back in once they work reliably. - - installation script now detects gentoo and avoids startup script installation since gentoo has it's own way of doing this. - - init scripts are now more friendly across linux distros, they were stupidly not so until now. - - ported the Berkeley DB env init pool change from the current branch. For some reason, using multiple dbs in a file requires this. I was not able to get a solid answer from sleepycat as to why. Downloads: http://osiris.shmoo.com/data/osiris-2.4.5-rc1.tar.gz http://osiris.shmoo.com/data/osiris-2.4.5-rc1-win32.exe Checksums: MD5(osiris-2.4.5-rc1.tar.gz)= e45522cf61ec2c57d01731bc8d0ad0e9 MD5(osiris-2.4.5-rc2-win32.exe)= 029b9d12b6c09070c13135d3ce6c7490 Please forward any questions or comments to the Osiris mailing list: osiris at shmoo.com, and any questions related to development to the development list: osiris-devel at shmoo.com - -- Brian Wotring ( brian at shmoo.com ) PGP KeyID: 0x9674763D -----BEGIN PGP SIGNATURE----- Version: PGP 8.0.3 - not licensed for commercial use: www.pgp.com iQA/AwUBQEDgqQ3seZ6WdHY9EQLI1gCdH5U8otQnHKa+eLFNrEfPRU0yK84AoIkW 46/K3IrijKGjQoW8dxyKI/pg =oasj -----END PGP SIGNATURE-----