On 9/29/14 5:18 PM, Yadin Flammer wrote:
> Not yet.  I was starting to wonder about that as I see apache2 went from
> 2.2.x to 2.4.x and I'm seeing a lot of changes were made that cause
> other issues, like all the default directory locations seem to have
> changed, so it's not unreasonable that the compiled cosign needs to be
> recompiled I guess...

The most recent cosign tar distribution on SourceForge won't build on 
2.4.x, due to other changes. If you're comfortable with a git pull and 
building 'configure', you can try a 3.2.1rc1:

On 8/22/14 5:02 PM, Liam Hoekenga wrote to cosign-discuss:
> I've pushed my proposed version of 3.2.1 to my own git repository - 
> https://github.com/lhoekenga/cosign
> The branch is cosign-3.2.1rc1.  Changes:
>
> 3.2.1rc1
>     filters: Apache 2.4.x support
>     cgi: Add frienddbname conf option
>     common: disable SSLv2 in the daemon and cgi
>
> I applied the upstream patches by hand.  I'm just learning to use git, 
> and wasn't sure if / how to get them out of the later branches in 
> which they appear.
>
> Could you it a try?  If it looks good, we'll see about getting a 
> release cut.

Or I can provide a private tar of 3.2.0 with a patch that allows it 
build with apache httpd 2.4 (contact me off-list).

-Phil

------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Cosign-discuss mailing list
Cosign-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cosign-discuss

Reply via email to