Query me this: why is your playback machine potentially at risk? Wouldnt it be better to have it not exposed directly to the Internet?
Steve Varholy President and General Manager [1478183502168_WXRY_Full_993_300x145.png] The Historic Barringer Building 1338 Main Street - Suite 202 Columbia, South Carolina 29201 Office: (803) 753-7260 x 251 Direct: (803) 404-5535 Cell: (703) 585-2101 A Service of the Independent Media Foundation ________________________________ From: Rick Thomas <[email protected]> Sent: Tuesday, May 16, 2017 7:38:54 PM To: Steve Varholy Cc: Rivendell Dev List; support Subject: Re: [RDD] Please fix this bug... That’s essentially option 2 by another name. It has the same problems. If doing it breaks something in Rivendell, we’re off the air. Perhaps one of the support folks can tell us which of the 4 update packages from the Paravel repo it’s safe to uncheck? Thanks! Rick > On May 16, 2017, at 3:11 PM, Steve Varholy <[email protected]> wrote: > > IIRC you can choose not to apply certain updates by unchecking them in the > Software Update dialog window. > > Sent from my iPhone > >> On May 16, 2017, at 6:07 PM, Rick Thomas <[email protected]> wrote: >> >> We are using the CentOS-6 that is part of the Rivendell Broadcast Appliance >> system from Paravel Systems. We have a paid-up support contract. It’s >> really great, and we love it a lot! Thanks for all the wonderful features! >> >> Now the problem: >> >> The Rivendell 2.15.3-1 update appears along with more than 300 other updates >> from CentOS when we run “yum check-update”. Some of those CentOS updates >> are important security fixes. So far as I know, there are no security >> issues with the Rivendell 2.15.3-1 package. >> >> However, if we hold off installing the Rivendell 2.15.3-1 update because we >> don’t want to deal with the bug in the attached mail from Fred Gleason, >> discovered by Ryan Williams, we are also holding off on installing all the >> security (and other) fixes from CentOS. >> >> We have two alternatives, as I see it. >> >> 1) What we’re doing now: hold off on any updates until the attached bug is >> fixed by Paravel Systems. >> >> or >> >> 2) Disable the Paravel Systems repo in the yum configuration files, thereby >> preventing the Rivendell 2.15.3-1 update from being applied — along with >> everything else from Paravel. We’ve never done this before (never needed >> to!) and we don’t know what it might break if we try it. If it breaks >> something in the Rivendell system, that will take us off the air, which we >> don’t want to do. >> >> So… >> >> Please fix the attached bug! >> >> Thanks! >> Rick Thomas >> SysAdmin, KPTZ 91.9 FM, Port Townsend, WA >> >> >>> On May 16, 2017, at 1:26 PM, Scott Spillers <[email protected]> >>> wrote: >>> >>> Rick, >>> We do not have any influence over development of the CentOS Linux >>> distribution, only the Rivendell code. What version of CentOS are you >>> using? CentOS 5 has reached end of life and is no longer updated. You may >>> want to consider updating to CentOS 7 if your version of the distro is no >>> longer supported. >>> >>> Scott Spillers >>> [email protected] >>> >>> On May 16, 2017 12:10 PM, "Rick Thomas" <[email protected]> wrote: >>> Dear Rivendell developers, >>> >>> We’ve been holding off installing the Rivendell2.15.3-1 update, hoping to >>> see a fix for this bug. >>> >>> But with all the activity over the NSA zero-day exploits released a few >>> months ago, it’s becoming imperative that we get the security updates from >>> CentOS that this is blocking. >>> >>> Please bump up the priority on this one… >>> >>> Thanks, >>> Rick Thomas, >>> SysAdmin KPTZ, 91.9 FM Port Townsend, WA >>> >>> >>>> ---------- Forwarded message --------- >>>> From: Fred Gleason <[email protected]> >>>> Date: Tue, Mar 28, 2017 at 8:05 AM >>>> Subject: Re: [RDD] Rivendell v2.15.3 >>>> To: User discussion about the Rivendell Radio Automation System >>>> <[email protected]> >>>> >>>>> On Mar 28, 2017, at 10:57, Ryan Williams <[email protected]> wrote: >>>>> I'm having an regression with the most recent release. If I open >>>>> RDLogEdit and try to add to a log's description it does not save. We use >>>>> the field field to add "READY" to the end of the description when the log >>>>> is cleared for air, so this one is going to sting a lot. >>>> Partially confirmed here. If you use the ‘Save’ button, the updated >>>> Description is indeed lost. However, clicking ‘OK’ (without clicking >>>> ‘Save’ first) appears to work normally. >>>> >>>> Cheers! >>>> >>>> |----------------------------------------------------------------------| >>>> | Frederick F. Gleason, Jr. | Chief Developer | >>>> | | Paravel Systems | >>>> |----------------------------------------------------------------------| >>>> | A room without books is like a body without a soul. | >>>> | -- Cicero | >>>> |----------------------------------------------------------------------| >>>> >>>> _______________________________________________ >>>> Rivendell-dev mailing list >>>> [email protected] >>>> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >> >> _______________________________________________ >> Rivendell-dev mailing list >> [email protected] >> http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
