<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>interesting. thanks.<br><br>wonder how easy it would be to slip an IP address disguised as a single decimal number in some code or even as some sort of list of escape sequences so no one would catch on.<br><br><br><br><br>----- Original Message -----<br>From: "Rhodium" <rhodium_uk@yahoo.co.uk><br>To: "John Huston" <fentonguy2003@yahoo.com>, "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Friday, March 5, 2010 4:21:53 PM GMT -05:00 US/Canada Eastern<br>Subject: Re: [cisco-voip] cisco licensing changes...<br><br>Here's a link about the life cycle of asterisk:<br><br>http://www.asterisk.org/developers/life-cycle<br><br>The last bit is the most important section... Its a common misconception and one I must admit to having when I first heard of "open source" but the more I delved into, the more I saw that there are checks in place to try and catch this stuff. I am not saying it doesnt happen at all, I am just saying that as with Cisco, you have an approval process for code so for something like that to happen, it has to be a big oversight. For example, if I am working on a bug to fix it, then I am only constrained to rectifying the bug. Not on any other unrelated code which has nothing to do with the feature or service I am working on. In that sense, I guess you can call it compartmentalised.<br><br>J<br><br><br><br>--- On Fri, 3/5/10, Lelio Fulgenzi <lelio@uoguelph.ca> wrote:<br><br>> From: Lelio Fulgenzi <lelio@uoguelph.ca><br>> Subject: Re: [cisco-voip] cisco licensing changes...<br>> To: "John Huston" <fentonguy2003@yahoo.com><br>> Cc: "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>> Date: Friday, March 5, 2010, 8:22 PM<br>> #yiv141557534 p<br>> {margin:0;}I'm<br>> not fully versed with open source and how it works, but is<br>> it possible that someone from the community can interject<br>> malicious code? I mean, I would gather that it wouldn't<br>> be in there long, but if it's like wikipedia, can't<br>> someone put in code that "phones home" and do some<br>> damage before someone retracts it?<br>> <br>> <br>> <br>> ---<br>> Lelio Fulgenzi, B.A.<br>> Senior Analyst (CCS) * University of Guelph * Guelph,<br>> Ontario N1G 2W1<br>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>> Cooking with unix is easy. You just sed it and forget it. <br>> <br>> - LFJ<br>> (with apologies to Mr. Popeil)<br>> <br>> <br>> ----- Original Message -----<br>> From: "John Huston"<br>> <fentonguy2003@yahoo.com><br>> To: "cisco-voip voyp list"<br>> <cisco-voip@puck.nether.net><br>> Sent: Friday, March 5, 2010 3:11:36 PM GMT -05:00 US/Canada<br>> Eastern<br>> Subject: Re: [cisco-voip] cisco licensing changes...<br>> <br>> K-12, small to medium business, with users<br>> being from under 10 up to 700. It's not for a<br>> Boeing, Lockeed, State or Fed gov. depolyment but<br>> Callmanager wasn't either when it came out.<br>> <br>> --- On Fri, 3/5/10, Bill Simon<br>> <bills@psu.edu> wrote:<br>> <br>> <br>> From: Bill Simon <bills@psu.edu><br>> Subject: Re: [cisco-voip] cisco licensing changes...<br>> To: "cisco-voip voyp list"<br>> <cisco-voip@puck.nether.net><br>> Date: Friday, March 5, 2010, 11:57 AM<br>> <br>> <br>> John Huston wrote:<br>> > Cisco is not crediting you for anything extra right<br>> now. While they have good product it's getting too<br>> expensive for a value to use type ratio, just like it is to<br>> run Microsoft products. We're seeing a move from<br>> Cisco to Juniper for routers and switches and then from<br>> Callmanager to Asterisk phone systems. They're<br>> cheaper to run and customers are not paying for featues they<br>> do not use often.<br>> <br>> Who's your demographic?<br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>> <br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>> <br>> -----Inline Attachment Follows-----<br>> <br>> _______________________________________________<br>> cisco-voip mailing list<br>> cisco-voip@puck.nether.net<br>> https://puck.nether.net/mailman/listinfo/cisco-voip<br>> <br><br><br><br></div></body></html>