Just curious, but why does it strike you as such a bad idea? Especially if
it was disabled by default. I can understand you not wanting your system
security or your personal privacy compromised, but I think it would be
great to have it in place for:
A) Manual activation for those who want
Andy Powell wrote:
...but the core of my 'problem' is software that calls home.
I agree a separate tool is possibly the best option here for privacy
reasons...
Simple solution seems to me, have a version.h file in each module and
rather then calling home publish the version info that is
I completely agree. This way you can get the same functionality on
demand instead of automatically.
-Original Message-
From: Duane [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 08, 2004 5:23 AM
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] res_motv: Request for Comment
Andy
I'm sure I haven't read all the relevant replies yet as I only completed
those who didn't break the thread.
My mindset would be to create a command line switch that returned the
int you mentioned that has the version details. This int could then be
fed to any app that could query your bugs
It might be nice if safe_asterisk (or some part of asterisk) e-mailed a
backtrace of the last asterisk .core file to Digium so they can see what
causes Asterisk to core dump. I've not had asterisk crash in that way,
but it might be nice for Digium.
On Tue, 6 Apr 2004, Mark Spencer wrote:
Hi,
-Original Message-
Now, of course, any time you put a call home feature in,
there are people who will be concerned about privacy.
Clearly it will be able to be disabled, but I want to run my
idea about deployment by everyone here and see if you guys
had some ideas. The
Hi
a) The idea itself -- is it a good one or is it stupid?
great idea. could be very useful if you don't have much time
to track/test cvs version and/or the bugtracker
b) The way to make it deployed without sneaking a call home in on
anybody that doesn't want it?
make it off by default,
I'd like to give this one 10 thumbs down. IMHO a bad idea, a nasty little bad idea..
evil, spawn of Satan. If this were implemented the first job of a new update would be
to rip it out and flush it down the nearest toilet.
I can only wait until we see M$ like activation implemented... oh the
Interesting idea, but needs some refinement...
Very few Asterisk installations are alike. I have a couple of FreeBSD asterisk
installations without any zaptel stuff, without ISDN, without MGCP, Skinny and
a lot of other modules stripped out. If any of those modules have a MAJOR bug,
it's not my
excellent idea.
eliot
On Tue, 2004-04-06 at 23:31, Mark Spencer wrote:
I've been considering the nature of Asterisk, its security, the bug
tracker, and more... And i've come up with an interesting idea: A
message of the version. The idea is that Asterisk has a compile
time
32-bit unsigned
Mark Spencer wrote:
Any feedback on:
a) The idea itself -- is it a good one or is it stupid?
Now this is just my views. No I do not feel we need to be sending any
information back unless we want to. Like someone else said a sub job that is
turned off by default. My preference would be no
I wouldn't want a call home feature that is enabled by default.
I think it would be great though if * had some ability to update itself.
Perhaps via a CLI command, as others have suggested. Something similar to
RH's up2date would be great in my opinion.
Anyway, thats my 2 cents.
Sean Rodger
Andy Powell Wrote:
I'd like to give this one 10 thumbs down. IMHO a bad idea, a nasty little
bad idea.. evil, spawn of Satan. If this were implemented the first job of
a new update would be to rip it out and flush it down the nearest toilet.
Just curious, but why does it strike you as such a
On Tue, 2004-04-06 at 23:31, Mark Spencer wrote:
Any feedback on:
a) The idea itself -- is it a good one or is it stupid?
I like the idea of being able to see what updates/fixes are available
vs. the code that I'm running. I think this would definitely be helpful
to me.
b) The way to make
Hi.
another (stupid) thing.
don't call that function motv. motv is a name
for another opensource project.
Matteo.
--
Matteo Brancaleoni
Espia System Administrator
Email : [EMAIL PROTECTED]
Web : http://www.espia.it
Phone : +39 02 70633354 - ext 201
IAX(2): [EMAIL PROTECTED] - ext 201
On Tue, 6 Apr 2004, Mark Spencer wrote:
I've been considering the nature of Asterisk, its security, the bug
tracker, and more... And i've come up with an interesting idea: A
message of the version. The idea is that Asterisk has a compile time
32-bit unsigned int version which is incremented
YES PLEASE.
Wonderful Stuff! In my opinion just what the project needs. I deployed and
supported many GPL and commercial SmoothWall (firewall) installs and was
forced to poll a web page from time to time to see if any of my customers
needed an urgent security patch applying...not a satisfactory
I'm keen on motv. I'll build a cgi wrapper for the logs if you need to
assign the task to someone.
TL
On Tue, 2004-04-06 at 23:31, Mark Spencer wrote:
I've been considering the nature of Asterisk, its security, the bug
tracker, and more... And i've come up with an interesting idea: A
On Tue, 6 Apr 2004, Mark Spencer wrote:
I've been considering the nature of Asterisk, its security, the bug
tracker, and more... And i've come up with an interesting idea: A
message of the version. The idea is that Asterisk has a compile time
32-bit unsigned int version which is incremented
b) The way to make it deployed without sneaking a call home in on
anybody that doesn't want it?
Enable by default, and inform people how to shut it off. Either way,
you'll piss someone off! ;) Might as well go for broke. :)
Why not just make available a CLI command that can be run on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 06 April 2004 11:31 pm, Mark Spencer wrote:
I've been considering the nature of Asterisk, its security, the bug
tracker, and more... And i've come up with an interesting idea: A
message of the version. The idea is that Asterisk has a
Any feedback on:
a) The idea itself -- is it a good one or is it stupid?
It's an excellent idea, another example of how committed Digium is to customer service!
b) The way to make it deployed without sneaking a call home in on
anybody that doesn't want it?
Make it so it has to be
22 matches
Mail list logo
