Hi Clemens,
- Dovecot still has an old copy of OpenSSL embedded that it uses for
those places that handle the TLS connection. I think that one is
unlikely given that you did rebuild dovecot and that it has been
revbumped. Nevertheless you should be able to rule it out by
Am 28.04.14 10:27, schrieb Winfried Dietmayer:
This is all really weird.
Thank you so far for your help , any further help is of course much appreciated.
Not sure, if this helps, but i just installed dovecot freshly from
macports on 10.9.2
with the default configuration, and it does not seem
Hi Winfried
I reinstalled dovecot from the MacPorts packages server but to no avail. The
vulnerability is still there.
OK, so we know it's not a statically linked OpenSSL (at least not in dovecot, it
might still be in one of dovecot's dependencies). Since those are only libiconv,
zlib and,
I have been trying to use MacPorts Ruby as the basis for deploying a
standalone Ruby-Tk app on Mavericks, just as many developers use MacPorts
Python (with PyQt, for instance). This was not working for me because Ruby
hard-codes its load path when built, so the binary and dylibs could not
Hi,
Is there any interest in supporting a relative variant for Ruby? The
portfile edit is trivial, cf below:
If that doesn't add too much runtime overhead or other unforseen
side-effects, why not enable it by default for all installations?
--
Clemens Lang
On Monday April 28 2014 15:45:13 Clemens Lang wrote:
Hi Winfried
I reinstalled dovecot from the MacPorts packages server but to no avail. The
vulnerability is still there.
[...]
To summerize:
- dovecot is vulnerable on my system regardless whether the binaries are
build via
On Apr 04, 2014, at 01:03, Ryan Schmidt wrote:
On Apr 3, 2014, at 17:51, René J.V. Bertin rjvber...@gmail.com wrote:
On Apr 04, 2014, at 00:33, Ryan Schmidt wrote:
What are the options here? I'm a bit amazed that this flag wasn't passed
in earlier dbus versions, as it's been around
I have the MacPorts ports of jarbundler (@2.2.0_0) and apache-ant (@1.9.3_0)
installed and active. I have the file JPortsUI.jar in the folder ~/jPorts.
Trying to make sense of the docs at http://informagen.com/JarBundler/, I
created in that same folder the file build.xml
taskdef
I have the MacPorts ports of jarbundler (@2.2.0_0) and apache-ant (@1.9.3_0)
installed and active. I have the file JPortsUI.jar in the folder ~/jPorts.
Trying to make sense of the docs at http://informagen.com/JarBundler/, I
created in that same folder the file build.xml
taskdef
OK, so I changed build.xml to:
?xml version=1.0?
project name=JPortsUI
taskdef name=jarbundler
classname=net.sourceforge.jarbundler.JarBundler /
/project
Now running ant build.xml gives a different error:
Buildfile: /Users/[myuserdirname]/jPorts/build.xml
BUILD FAILED
According to ant.apache.org/manual/running.html
All JARs in $ANT_HOME/lib were added to the $CLASSPATH automatically, and
perhaps now also $HOME/.ant/lib
Ant further takes the -lib argument for passing further specific paths.
Does setting the path to the missing class solve the issue?
On Apr
I get no error if I use:
ant -lib /opt/local/share/java -buildfile build.xml
However, I don't find afterward any JPortsUI.app. (Creating that was the whole
point.)
In case it's relevant:
(i)echo $ANT_HOME gives empty response.
(ii) I have no $HOME/.ant/lib (presuming that $HOME refers
12 matches
Mail list logo
