Skip to content
Snippets Groups Projects
  1. May 05, 2011
  2. Feb 10, 2011
  3. Feb 09, 2011
  4. Jan 24, 2011
  5. Jan 19, 2011
  6. Jan 06, 2011
  7. Jan 04, 2011
  8. Dec 17, 2010
  9. Dec 07, 2010
  10. Nov 18, 2010
  11. Nov 05, 2010
  12. Oct 22, 2010
    • Terry Wilson's avatar
      Merged revisions 292825 via svnmerge from · 8ea287b0
      Terry Wilson authored
      https://origsvn.digium.com/svn/asterisk/branches/1.8
      
      ........
        r292825 | twilson | 2010-10-22 15:35:29 -0700 (Fri, 22 Oct 2010) | 4 lines
        
        Don't create directories without at least o+x
        
        Also, making files that you are going to modify read-only is dumb.
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@292826 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      8ea287b0
    • Terry Wilson's avatar
      Merged revisions 292794 via svnmerge from · 3d658dce
      Terry Wilson authored
      https://origsvn.digium.com/svn/asterisk/branches/1.8
      
      ........
        r292794 | twilson | 2010-10-22 15:18:36 -0700 (Fri, 22 Oct 2010) | 2 lines
        
        Make files readable only by the owner
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@292808 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      3d658dce
    • Leif Madsen's avatar
      Merged revisions 292787 via svnmerge from · 8de8e4a1
      Leif Madsen authored
      https://origsvn.digium.com/svn/asterisk/branches/1.8
      
      ................
        r292787 | lmadsen | 2010-10-22 16:28:43 -0500 (Fri, 22 Oct 2010) | 21 lines
        
        Merged revisions 292786 via svnmerge from 
        https://origsvn.digium.com/svn/asterisk/branches/1.6.2
        
        ........
          r292786 | lmadsen | 2010-10-22 16:16:12 -0500 (Fri, 22 Oct 2010) | 13 lines
          
          Update the LDIF file for LDAP.
          The LDIF file asterisk.ldif was quite a bit out of date from the asterisk.ldap-schema file, so I've
          now updated that to be in sync. The asterisk.ldif file being out of sync was a problem on my systems
          where I was doing an ldapadd to import the schema into the LDAP database, and the existing file
          would cause problems and ERROR messages when registering.
          
          Additional documention has been added based on feedback in the issue I'm closing.
          
          (closes issue #13861)
          Reported by: scramatte
          Patches:
                ldap-update.txt uploaded by lmadsen (license 10)
          Tested by: lmadsen, jcovert, suretec, rgenthner
        ........
      ................
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@292788 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      8de8e4a1
    • Terry Wilson's avatar
      Merged revisions 292740 via svnmerge from · 89a16f9c
      Terry Wilson authored
      https://origsvn.digium.com/svn/asterisk/branches/1.8
      
      ........
        r292740 | twilson | 2010-10-22 09:49:34 -0700 (Fri, 22 Oct 2010) | 45 lines
        
        Add TLS cert helper script
        
        This script is useful for quickly generating self-signed CA, server, and client
        certificates for use with Asterisk. It is still recommended to obtain
        certificates from a recognized Certificate Authority and to develop an
        understanding how SSL certificates work. Real security is hard work.
        
        OPTIONS:
          -h  Show this message
          -m  Type of cert "client" or "server". Defaults to server.
          -f  Config filename (openssl config file format)
          -c  CA cert filename (creates new CA cert/key as ca.crt/ca.key if not passed)
          -k  CA key filename
          -C  Common name (cert field)
                For a server cert, this should be the same address that clients
                attempt to connect to. Usually this will be the Fully Qualified
                Domain Name, but might be the IP of the server. For a CA or client
                cert, it is merely informational. Make sure your certs have unique
                common names.
          -O  Org name (cert field)
                An informational string (company name)
          -o  Output filename base (defaults to asterisk) 
          -d  Output directory (defaults to the current directory)
        
        Example:
        
        To create a CA and a server (pbx.mycompany.com) cert with output in /tmp:
          ast_tls_cert -C pbx.mycompany.com -O "My Company" -d /tmp
        
        This will create a CA cert and key as well as asterisk.pem and the the two
        files that it is made from: asterisk.crt and asterisk.key. Copy asterisk.pem
        and ca.crt somewhere (like /etc/asterisk) and set tlscertfile=/etc/asterisk.pem
        and tlscafile=/etc/ca.crt. Since this is a self-signed key, many devices will
        require you to import the ca.crt file as a trusted cert.
        
        To create a client cert using the CA cert created by the example above:
          ast_tls_cert -m client -c /tmp/ca.crt -k /tmp/ca.key -C "Joe User" -O \
            "My Company" -d /tmp -o joe_user
        
        This will create client.crt/key/pem in /tmp. Use this if your device supports
        a client certificate. Make sure that you have the ca.crt file set up as
        a tlscafile in the necessary Asterisk configs. Make backups of all .key files
        in case you need them later.
      ........
      
      
      git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@292743 65c4cc65-6c06-0410-ace0-fbb531ad65f3
      89a16f9c
  13. Oct 21, 2010
  14. Oct 19, 2010
  15. Oct 02, 2010
  16. Sep 16, 2010
  17. Sep 14, 2010
  18. Aug 03, 2010
  19. Jul 28, 2010
  20. Jul 20, 2010
  21. Jul 16, 2010
  22. Jul 15, 2010
  23. Jul 13, 2010
  24. Jun 21, 2010
  25. Jun 09, 2010
Loading