You could try enclosing the header file in
extern C {
...
}
but it's not an ellegant solution.
--
Andrzej Godziuk
http://CloudAccess.net/
Hi,
the subject might suggest the message is an off-topic
for the list.
Actually this problem arose in the early stages of the analysis
and design of a software component that eventually could be
merged with the libraries that come with mod_rivet.
To put it simple my question is: can every
2011/3/9 Massimo Manghi massimo.man...@unipr.it:
the subject might suggest the message is an off-topic
for the list.
Technically it is, d...@apr.apache.org would have been a better place for it.
To put it simple my question is: can every module in APR be used
also to build standalone
On Wed, 9 Mar 2011 00:28:44 +0100, Ben Noordhuis wrote:
2011/3/9 Massimo Manghi massimo.man...@unipr.it:
the subject might suggest the message is an off-topic
for the list.
Technically it is, d...@apr.apache.org would have been a better place
for it.
ok Ben, thank you. I will
--
Am 08.03.2011 07:06, schrieb William A. Rowe Jr.:
But what does this have to do with httpd? At best, you are suggesting a docs
improvement.
Otherwise this is on the language you are using and not an ASF issue... but the
desired
behavior has been part of Crypt::PasswdMD5 for a dozen years,
From the peanut gallery:
Oh dear.
The password encryption is called MD5 based crypt (as opposed to the DES
based crypt used in the early days by various systems). MD5 based crypt
is now standard with modern systems. There's nothing Apache-special about
the algorithm. We just use a different
This is forwarded to the OP (CC'd) , thanks for clearing up a few things
for me as well, and perhaps the docs could be amended to reflect it is
not base md5, remember, most admins out there are not encryption
experts.
Incidentally, when will httpd accept sha2? Planned in 2.2.x? or only
2.3/4.x ?
On 3/8/2011 5:47 PM, Noel Butler wrote:
Incidentally, when will httpd accept sha2? Planned in 2.2.x? or only 2.3/4.x
?
We won't implement the hash itself... so it would likely originate from tighter
integration with openssl (which would give us DES_crypt for legacy win32
compatibility).
