You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Clayton Keller <in...@ruraltel.net> on 2010/10/21 21:30:10 UTC

Latest Version Query

Is there an available/preferred method to query for the most recent 
released version of SpamAssassin?

I know there exists TXT records to for each version to maintain 
sa-update based rules (i.e. 1.3.3.updates.spamassassin.org). But does 
something exist to query and indicate that the current version is, for 
example 3.3.1?

Rather than say scraping the "Released version" line from the Downloads 
page, I was looking for a DNS related query to easily provide the most 
current stable release.

At this point, have I just overlooked something on the Wiki or in the docs?

Clay

Re: Latest Version Query

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Thu, 2010-10-21 at 16:59 -0500, Clayton Keller wrote:
> On 10/21/2010 4:19 PM, Karsten Bräckelmann wrote:

> > I don't assume you will have that script do an unattended upgrade, would
> > you? Not a wise idea, in case some more fundamental things change like
> > with 3.3.
> >
> > So the script would notify you by mail? What would be the difference to
> > the announce list?
> 
> Unattended upgrades were not my intention. I am as leery of that as you are.
> 
> At this point I was just looking at different ways to determine the 
> current stable release version available with the least amount of human 
> interaction.
> 
> Thank you for the added feedback.

Well, if you ultimately want some tool to monitor new releases of
various software (not SA only), I guess it should be trivial for the SA
bit to parse out of the download page, CPAN, an FTP mirror listing, or
services like freshmeat (RSS?).

If all you want is to be notified about updates of various software,
subscribing (possibly a role account) to each software's announce list
should do. It's generally *very* low-volume and hardly requires any
human interaction at all -- unless there's a new release. Sic!

If you want this basically for SA only, the announce list *is* the way
to go IMHO. Low volume, no interaction overhead whatsoever, and trivial
and quick to implement.


Since you mentioned ClamAV and how they do it -- it is my understanding
the version prefix in the "current" TXT record is not meant for any kind
of human monitoring itself -- but a way to allow freshclam to pester and
annoy the hell out of sysadmins watching the logs.

Something SA and sa-update does not do. Given the release history of
both these projects, and the number of added features and major changes
during the last two years, it seems to be warranted for Clam. It's a
different story with SA.

Even more so since 3.3, as we are migrating towards a workflow of more
frequent rule updates, independent of changes in the rather stable code
base.


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: Latest Version Query

Posted by Clayton Keller <in...@ruraltel.net>.
On 10/21/2010 4:19 PM, Karsten Bräckelmann wrote:
> On Thu, 2010-10-21 at 16:01 -0500, Clayton Keller wrote:
>> On 10/21/2010 3:43 PM, John Hardin wrote:
>
>>>> Is there an available/preferred method to query for the most recent
>>>> released version of SpamAssassin?
>>>>
>>>> I know there exists TXT records to for each version to maintain
>>>> sa-update based rules (i.e. 1.3.3.updates.spamassassin.org). But does
>>>> something exist to query and indicate that the current version is, for
>>>> example 3.3.1?
>
>>> As an update package is released with each base code release, you can
>>> iterate the TXT records until you get no response. If you already have
>>> SA installed and you want to see if a newer version is available, that's
>>> three queries: current.current.current+1, current.current+1.0, and
>>> current+1.0.0
>
> Unfortunately, not *that* easy. I am not entirely sure about the exact
> details, but -- the respective next version also is available,
> corresponding to running off of the SVN branch.
>
>    $ host -t TXT 2.3.3.updates.spamassassin.org
>    2.3.3.updates.spamassassin.org descriptive text "1004932"
>
> Same for 3.4.0, FWIW. The problem now is the exact timing. Or lack
> thereof, which was not an issue with previous releases but became an
> issue since 3.3.0 -- which split out rules from code in a separate
> tarball. I believe to recall that setting up the 3.4.0 channel took a
> while, so the above method would have failed to alert you about the
> availability of 3.3.0.

Thank you for bringing this to my attention.

>
> What *does* work, however, is subscribing to the announce list. This
> would reliably and timely notify you of a new release.
>
>
>> That's kind of the direction I was beginning to go myself with what's
>> available at the present time.
>>
>> Would there be interest in adding a TXT record which would respond with
>> the most current version, the most current sa-update response for that
>> version, etc.? I was thinking of something similar to ClamAV's
>> current.cvd.clamav.net TXT entry.
>
> What would be wrong about the announce list?
>
> I don't assume you will have that script do an unattended upgrade, would
> you? Not a wise idea, in case some more fundamental things change like
> with 3.3.
>
> So the script would notify you by mail? What would be the difference to
> the announce list?
>
>

Unattended upgrades were not my intention. I am as leery of that as you are.

At this point I was just looking at different ways to determine the 
current stable release version available with the least amount of human 
interaction.

Thank you for the added feedback.



Re: Latest Version Query

Posted by Karsten Bräckelmann <gu...@rudersport.de>.
On Thu, 2010-10-21 at 16:01 -0500, Clayton Keller wrote:
> On 10/21/2010 3:43 PM, John Hardin wrote:

> > > Is there an available/preferred method to query for the most recent
> > > released version of SpamAssassin?
> > >
> > > I know there exists TXT records to for each version to maintain
> > > sa-update based rules (i.e. 1.3.3.updates.spamassassin.org). But does
> > > something exist to query and indicate that the current version is, for
> > > example 3.3.1?

> > As an update package is released with each base code release, you can
> > iterate the TXT records until you get no response. If you already have
> > SA installed and you want to see if a newer version is available, that's
> > three queries: current.current.current+1, current.current+1.0, and
> > current+1.0.0

Unfortunately, not *that* easy. I am not entirely sure about the exact
details, but -- the respective next version also is available,
corresponding to running off of the SVN branch.

  $ host -t TXT 2.3.3.updates.spamassassin.org
  2.3.3.updates.spamassassin.org descriptive text "1004932"

Same for 3.4.0, FWIW. The problem now is the exact timing. Or lack
thereof, which was not an issue with previous releases but became an
issue since 3.3.0 -- which split out rules from code in a separate
tarball. I believe to recall that setting up the 3.4.0 channel took a
while, so the above method would have failed to alert you about the
availability of 3.3.0.

What *does* work, however, is subscribing to the announce list. This
would reliably and timely notify you of a new release.


> That's kind of the direction I was beginning to go myself with what's 
> available at the present time.
> 
> Would there be interest in adding a TXT record which would respond with 
> the most current version, the most current sa-update response for that 
> version, etc.? I was thinking of something similar to ClamAV's 
> current.cvd.clamav.net TXT entry.

What would be wrong about the announce list?

I don't assume you will have that script do an unattended upgrade, would
you? Not a wise idea, in case some more fundamental things change like
with 3.3.

So the script would notify you by mail? What would be the difference to
the announce list?


-- 
char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}


Re: Latest Version Query

Posted by Clayton Keller <in...@ruraltel.net>.
On 10/21/2010 3:43 PM, John Hardin wrote:
> On Thu, 21 Oct 2010, Clayton Keller wrote:
>
>> Is there an available/preferred method to query for the most recent
>> released version of SpamAssassin?
>>
>> I know there exists TXT records to for each version to maintain
>> sa-update based rules (i.e. 1.3.3.updates.spamassassin.org). But does
>> something exist to query and indicate that the current version is, for
>> example 3.3.1?
>>
>> Rather than say scraping the "Released version" line from the
>> Downloads page, I was looking for a DNS related query to easily
>> provide the most current stable release.
>
> As an update package is released with each base code release, you can
> iterate the TXT records until you get no response. If you already have
> SA installed and you want to see if a newer version is available, that's
> three queries: current.current.current+1, current.current+1.0, and
> current+1.0.0
>
Thanks for the reply John.

That's kind of the direction I was beginning to go myself with what's 
available at the present time.

Would there be interest in adding a TXT record which would respond with 
the most current version, the most current sa-update response for that 
version, etc.? I was thinking of something similar to ClamAV's 
current.cvd.clamav.net TXT entry.

Re: Latest Version Query

Posted by John Hardin <jh...@impsec.org>.
On Thu, 21 Oct 2010, Clayton Keller wrote:

> Is there an available/preferred method to query for the most recent released 
> version of SpamAssassin?
>
> I know there exists TXT records to for each version to maintain sa-update 
> based rules (i.e. 1.3.3.updates.spamassassin.org). But does something exist 
> to query and indicate that the current version is, for example 3.3.1?
>
> Rather than say scraping the "Released version" line from the Downloads page, 
> I was looking for a DNS related query to easily provide the most current 
> stable release.

As an update package is released with each base code release, you can 
iterate the TXT records until you get no response. If you already have SA 
installed and you want to see if a newer version is available, that's 
three queries: current.current.current+1, current.current+1.0, and 
current+1.0.0

-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org    FALaholic #11174     pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   Judicial Activism (n): interpreting the Constitution to grant the
   government powers that are popularly felt to be "needed" but that
   are not explicitly provided for therein (common definition);
   interpreting the Constitution as it is written (Brady definition)
-----------------------------------------------------------------------
  57 days until TRON Legacy