[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #15910 [Applications/Tor Browser]: Figure out what to do with OpenH264 (downloads) in Tor Browser



#15910: Figure out what to do with OpenH264 (downloads) in Tor Browser
--------------------------------------+--------------------------
 Reporter:  gk                        |          Owner:  tbb-team
     Type:  task                      |         Status:  assigned
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:  ff60-esr                  |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+--------------------------

Comment (by sysrqb):

 Replying to [comment:19 cypherpunks]:
 > Replying to [comment:5 gk]:
 > > The download URL looks something like:
 http://ciscobinary.openh264.org/openh264-linux32-4adf9cd6dd1358eefe3cbb5eddbfbf4ff06cfa65.zip
 > >
 > > Yes, HTTP and no deterministic build. *headdesk*
 > There are no MinGW URLs.
 > They offer to build it yourself https://github.com/cisco/openh264#for-
 windows-builds.

 comment:20 :
 {{{
 Q: If I use the source code in my product, and then distribute that
 product on my
 own, will Cisco cover the MPEG LA licensing fees which I'd otherwise have
 to pay?

 A: No. Cisco is only covering the licensing fees for its own binary
 module, and
 products or projects that utilize it must download it at the time the
 product or
 project is installed on the user's computer or device. Cisco will not be
 liable for
 any licensing fees incurred by other parties.
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15910#comment:30>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs