<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/docsis/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/docsis/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 02 Jun 2013 14:02:05 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/docsis/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=25#a22e/9710/2d90</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Link to my post to debian-legal: &lt;a href="http://lists.debian.org/debian-legal/2013/06/msg00001.html" rel="nofollow"&gt;http://lists.debian.org/debian-legal/2013/06/msg00001.html&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lisandro D. N. Pérez Meyer</dc:creator><pubDate>Sun, 02 Jun 2013 14:02:05 -0000</pubDate><guid>https://sourceforge.netd02056c7a5f904b53f9fc03413d33b63396e4e2b</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=25#a22e/9710</link><description>&lt;div class="markdown_content"&gt;&lt;blockquote&gt;
&lt;p&gt;Yes, but what CRYPTOGRAPHY does docsis use via libsnmp?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;IANAL, but as far as I understand, it doesn't needs to use it, just link. The problem here is that there is a library in the middle which is using libopenssl. According to some people this situation will require an OpenSSL exception, according to some others, not.&lt;/p&gt;
&lt;p&gt;I have just sent a mail to debian-legal (will post link as soon as I have it) to ask them for their advice on the situation.&lt;/p&gt;
&lt;p&gt;I'm sure this is not the only software which got involved in this change, so we will need to see what happens.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lisandro D. N. Pérez Meyer</dc:creator><pubDate>Sun, 02 Jun 2013 14:01:16 -0000</pubDate><guid>https://sourceforge.net1991fef788e2cd0a6c4f3bf23272ad4d9b80710e</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=50#c6dd</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; pending&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Laager</dc:creator><pubDate>Sun, 02 Jun 2013 04:40:35 -0000</pubDate><guid>https://sourceforge.netfaff450e16b7d80b61eef7554d4339f6cb2d1fdf</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=50#de42/5ad1</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;Some time ago, I ask the original author, Cornel Ciocirlan, for change the license to the gpl with the openssl exception, and he answer ok to the change, but he forgot to change the license... and after that it was impossible to me to contact with him to confirm the license change...&lt;/p&gt;
&lt;p&gt;So I only have a "verbal" approval :(&lt;/p&gt;
&lt;p&gt;By the way, docsis don't use ssl encription, but use libsnmp that is linked with openssl for implement snmp v3 protocol... that docsis don't use...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Eduardo Ferro Aldama</dc:creator><pubDate>Fri, 31 May 2013 08:47:09 -0000</pubDate><guid>https://sourceforge.netefcb30355a40bc5a1e3a7a3f6047207b4248b9e1</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=50#a22e</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, but what CRYPTOGRAPHY does docsis use via libsnmp?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Laager</dc:creator><pubDate>Fri, 31 May 2013 06:01:52 -0000</pubDate><guid>https://sourceforge.net9319da56e6490df97c10c023e0a3bc7d56c88239</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=25#56c2</link><description>&lt;div class="markdown_content"&gt;&lt;blockquote&gt;
&lt;p&gt;Is docsis one of those applications?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;yes, it links to libsnmp which in turn links to libopenssl&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;what about providing a second binary of libsnmp that does not&lt;br /&gt;
have the SSL functionality?&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;It will not happen :(&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lisandro D. N. Pérez Meyer</dc:creator><pubDate>Fri, 31 May 2013 01:17:27 -0000</pubDate><guid>https://sourceforge.netf53347218f2c765c68e09b42e440c532e54b91cc</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=50#077b</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Is docsis one of those applications? I can't think of how it would be, but I'm not an expert, I'm really just slightly maintaining a more-or-less abandoned package. If not, what about providing a second binary of libsnmp that does not have the SSL functionality?&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Laager</dc:creator><pubDate>Fri, 31 May 2013 00:32:15 -0000</pubDate><guid>https://sourceforge.net994fc068dd57322304318e5d787e9a467a4edd1a</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=25#0452/4a7d</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The last version of libsnmp has added a direct link to -lcrypto, triggering the error in lintian (the app that does static analysis of Debian packages).&lt;/p&gt;
&lt;p&gt;But libsnmp had already depended on libssl :-/&lt;/p&gt;
&lt;p&gt;Yes, there are applications that depend on this behaviour. No, I really doubt we will see a libsnmp without OpenSSL or linked against GNUTLS :-(&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lisandro D. N. Pérez Meyer</dc:creator><pubDate>Fri, 31 May 2013 00:25:35 -0000</pubDate><guid>https://sourceforge.net58c50b760752216d39eb61af7a84de4119bce856</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=50#0452</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Why does libsnmp link to OpenSSL? Are there applications in Debian which depend on that behavior? If not, obviously eliminating that linkage entirely is the simplest answer. Assuming there are users of it, would it be possible to have the libsnmp source package be compiled a second time without that linkage to create a libsnmp-nossl binary package which docsis could use.&lt;/p&gt;
&lt;p&gt;If so, isn't this academic? If docsis could be compiled against a libsnmp that doesn't use OpenSSL and work perfectly fine, then how do we have a problem?&lt;/p&gt;
&lt;p&gt;Alternatively, could libsnmp link against GnuTLS? I think it has some level of OpenSSL source-compatbility (e.g. a porting layer).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Richard Laager</dc:creator><pubDate>Fri, 31 May 2013 00:09:28 -0000</pubDate><guid>https://sourceforge.net003396a1d3b6e7bdacaff3688e4513c5edeb67b4</guid></item><item><title>#21 docsis build depends on lin</title><link>https://sourceforge.net/p/docsis/bugs/21/?limit=25#de42</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;By the way, this change is needed to keep docsis in Debian :-/&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Lisandro D. N. Pérez Meyer</dc:creator><pubDate>Tue, 28 May 2013 16:18:06 -0000</pubDate><guid>https://sourceforge.netb111801569b1ecd7043ec561663da132fd0460e8</guid></item></channel></rss>