At Fri, 01 Apr 2011 11:34:34 +0200, Christian Roessner wrote: > > > SOPE and SOGo use OpenSSL which is incompatible with the GPL due to > > the advertising clause. There are only 3 places where OpenSSL is used > > and it shouldn't be that hard to replace OpenSSL with GnuTLS or > > NSS. Would a patch doing that be accepted? > > I know, I will get flamed right now, but please do not use gnutls. > Google for i.e. OpenLDAP and gnutls and follow the comments from Howard > Chu, then you understand me. Or at least dear SOGo devs: please do not > drop packges for Ubuntu/Debian on inverse, so people can use the openssl > variant.
There is no need to flame people who raise valid concerns. I was actually thinking about using NSS instead of GnuTLS, but I don't have a very strong opinion about it. I did have some problems with GnuTLS a few years ago, but those problems might have been solved and I don't have experience with NSS to compare with. Do you (of anyone else on this list) know of any potential problem with using NSS? > My personal opinion: If I as a user have to choose between license and a > working ssl implementation, I choose the latter one. If you actually read the whole thread you also see that people aren't fond of using GnuTLS, but don't have the choice of using OpenSSL. As user you can do with GPL software whatever you want as long as you don't distributie it, but as a developer or distribution you can't just violate the license of other people's code. And Inverse could add an exception for linking with OpenSSL, but that wouldn't fix the problem with OpenChange or other GPL code used by SOGo now or in the future. So in my opinion the best solution would be to just use a GPL-compatible SSL library. > > SOGo configuration file is currently in /home/sogo. For the FHS this > > should be under /etc. A quick way to do this is to give the sogo user > > a homedirectory of /etc/sogo, but I think that's bit dirty. Would it > > be possible to use something like /etc/sogo/sogo.conf instead of the > > GNUdefaults in the sogo homedirectory? Or maybe something like > > /etc/GNUstep/Defaults? I don't really know enough about GNUstep to > > figure out the best way to do this. > > I just think a about packages like amavis. The home is /var/lib/amavis. > If you set up razor or pyzor, you do have the configuration in > /var/lib/amavis, too. So in my opinion there do exist projects and > packages, where it is normal that the configuration might be elsewhere. > Compared to sogo, you even would not directly edit the plist, would you? > If so, maybe you could place a symlink into /etc/sogo/sogo.plist? Just > an idea. What I currently do on my own server is to edit an old-style configuration file and copy that in place everytime I change it, so I don't have to edit the XML file. I think that's a bit suboptimal. Some time ago someone also posted a script that parses a SOGo.conf and generated the poperty list. So there are more people who don't like that GNUstep changes the configuration automatically to XML (or worse, overwrite it when it can't parse it). So maybe it's better to make changes in the way SOGo is configured, but I would like to know the opinion of the SOGo developers about this. > Sorry for my comments above. Just my opinion and experiences. Again, no need to apologize. Discussions like this only make SOGo a better product. Jeroen Dekkers -- users@sogo.nu https://inverse.ca/sogo/lists
