Apache Subversion server hosting files via WebDAV [central repository] [tortoisesvn]

Q: I have a server set up on my desktop using Apache 2.059 (2.24 is not up with the right instructions I used .) but I

I Subversion and set up a Subversion server, so we are working on a project with a .

We would like to use SSL for patent protection in the future, I found instructions in the Tortoise help file (from here: http://.net/downloads) to set up SSL on an Apache server, but I got a snag.

When I go to a SSL certificate with the files from here to generate: http://hunter.campbus.com/
and an SSL config file from here: http://tud.at / programm / openssl.cnf modified according to instructions, with the command: bin openssl req-config openssl.cnf-new-bin-server.csr mine freezes at 100% CPU usage (well, 50%, but it is a dual core) after saying “Loading screen into random state -”

I run for a while thinking that encode something, but it seems simply stuck.

Any suggestions about making the certificate or can someone point me a good guide? I am using the instructions here: http://.net/docs/release/Tor.ersetup.html # tsvn-server setup apache-7 (http://.net/docs/release/ TortoiseSVN_en / # tsvn tsvn-serversetup.html server setup apache-7)

Thanks in advance!


Re:Here is a site that offers free SSL certs. If I remember correcty they are a CA for most browsers except IE.

http://cert.startcom.org/

John


Re:guy, in a small environment, hand-installing a new CA cert is easy. In a large environment, it's easily scripted.

For which browser? IE, FF and Opera all use different trusted cert stores AFAIK.


Re:guy, in a small environment, hand-installing a new CA cert is easy. In a large environment, it's easily scripted.

Re:Originally posted by: guy

Yeah, sorry; that is the problem but there's no way I'd pay for one when you CAN generate one.

The problem, if you consider it that, is that everyone connecting to your server will get a dialog asking them if they really want to connect because the certificate isn't signed by a trusted CA. You could always give them your CA cert, once you get it all worked out of course, and have them import that into their trusted list but doing that for everyone is usually a PITA.

This is only for me and three other team members, though…


Re:Yeah, sorry; that is the problem but there's no way I'd pay for one when you CAN generate one.

The problem, if you consider it that, is that everyone connecting to your server will get a dialog asking them if they really want to connect because the certificate isn't signed by a trusted CA. You could always give them your CA cert, once you get it all worked out of course, and have them import that into their trusted list but doing that for everyone is usually a PITA.


Re:Originally posted by: guy

Originally posted by: guy
Well, but I could generate my own easily enough and I didn't really do anything to "build" my server in the first place. :P I guess I misunderstood your question. It sounded like you were having problems generating a Certificate:

"Any suggestions on creating the certificate or could anyone point me to a good guide?"

Yeah, sorry; that is the problem but there's no way I'd pay for one when you CAN generate one.


Re:Originally posted by: guy
Well, but I could generate my own easily enough and I didn't really do anything to "build" my server in the first place. :P I guess I misunderstood your question. It sounded like you were having problems generating a Certificate:

"Any suggestions on creating the certificate or could anyone point me to a good guide?"


Re:Originally posted by: guy
If your only issue is creating an SSL certificate, you can always buy one for $20 a year or less. Less work than rebuilding your server.

Well, but I could generate my own easily enough and I didn't really do anything to "build" my server in the first place. :P


Re:If your only issue is creating an SSL certificate, you can always buy one for $20 a year or less. Less work than rebuilding your server.

Re:guy, it'll be easier and more reliable. That's the environment Apache, mod_ssl, and Subversion are most tested in.

Re:No, this is a university setting; we're actually about to move this to an off-campus server (at a team member's house) so we can all access it from wherever (the university has all kinds of firewalls…).

So, you're saying to essentially go with linux anyway; we might do that in the end depending on what's on this other computer. I do have a spare Linux box sitting around…


Re:guy, what you're doing is technically possible but not mainstream and therefore unlikely to be as tested. That's not what I would want on my SCM server.

You'd be well served to set up a Linux box to host this, just because that's what other people who are doing what you are doing use. I infer from your wording that this is for a business purpose; in a business environment, a spare PC isn't that expensive and if you're not dedicating a machine for your SCM server you need to do so anyway.


Re:Sorry, can't help you then….

Re:Distro, no, this is on XP Pro. :P

Re:Text (http://www.howtoforge.com/debian_subversion_websvn)

this guide worked great for me on my Deb server. You didn't say which distro, but the configs should be close.


Related posts

Leave a comment

0 Comments.

Leave a Reply


click to changeSecurity Code

[ Ctrl + Enter ]