Advertisement
Guest User

Untitled

a guest
Dec 2nd, 2015
276
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
Bash 5.08 KB | None | 0 0
  1. Welcome to Ubuntu 15.04 (GNU/Linux 2.6.32-34-pve x86_64)
  2.  
  3.  * Documentation:  https://help.ubuntu.com/
  4. Last login: Mon Nov 30 11:00:53 2015 from mailer3.rapidtvnews.com
  5. root@aidapgsql94:~# cat /etc/postgresql/9.4/main/pg_hba.conf
  6. # PostgreSQL Client Authentication Configuration File
  7. # ===================================================
  8. #
  9. # Refer to the "Client Authentication" section in the PostgreSQL
  10. # documentation for a complete description of this file.  A short
  11. # synopsis follows.
  12. #
  13. # This file controls: which hosts are allowed to connect, how clients
  14. # are authenticated, which PostgreSQL user names they can use, which
  15. # databases they can access.  Records take one of these forms:
  16. #
  17. # local      DATABASE  USER  METHOD  [OPTIONS]
  18. # host       DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
  19. # hostssl    DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
  20. # hostnossl  DATABASE  USER  ADDRESS  METHOD  [OPTIONS]
  21. #
  22. # (The uppercase items must be replaced by actual values.)
  23. #
  24. # The first field is the connection type: "local" is a Unix-domain
  25. # socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
  26. # "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
  27. # plain TCP/IP socket.
  28. #
  29. # DATABASE can be "all", "sameuser", "samerole", "replication", a
  30. # database name, or a comma-separated list thereof. The "all"
  31. # keyword does not match "replication". Access to replication
  32. # must be enabled in a separate record (see example below).
  33. #
  34. # USER can be "all", a user name, a group name prefixed with "+", or a
  35. # comma-separated list thereof.  In both the DATABASE and USER fields
  36. # you can also write a file name prefixed with "@" to include names
  37. # from a separate file.
  38. #
  39. # ADDRESS specifies the set of hosts the record matches.  It can be a
  40. # host name, or it is made up of an IP address and a CIDR mask that is
  41. # an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that
  42. # specifies the number of significant bits in the mask.  A host name
  43. # that starts with a dot (.) matches a suffix of the actual host name.
  44. # Alternatively, you can write an IP address and netmask in separate
  45. # columns to specify the set of hosts.  Instead of a CIDR-address, you
  46. # can write "samehost" to match any of the server's own IP addresses,
  47. # or "samenet" to match any address in any subnet that the server is
  48. # directly connected to.
  49. #
  50. # METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
  51. # "ident", "peer", "pam", "ldap", "radius" or "cert".  Note that
  52. # "password" sends passwords in clear text; "md5" is preferred since
  53. # it sends encrypted passwords.
  54. #
  55. # OPTIONS are a set of options for the authentication in the format
  56. # NAME=VALUE.  The available options depend on the different
  57. # authentication methods -- refer to the "Client Authentication"
  58. # section in the documentation for a list of which options are
  59. # available for which authentication methods.
  60. #
  61. # Database and user names containing spaces, commas, quotes and other
  62. # special characters must be quoted.  Quoting one of the keywords
  63. # "all", "sameuser", "samerole" or "replication" makes the name lose
  64. # its special character, and just match a database or username with
  65. # that name.
  66. #
  67. # This file is read on server startup and when the postmaster receives
  68. # a SIGHUP signal.  If you edit the file on a running system, you have
  69. # to SIGHUP the postmaster for the changes to take effect.  You can
  70. # use "pg_ctl reload" to do that.
  71.  
  72. # Put your actual configuration here
  73. # ----------------------------------
  74. #
  75. # If you want to allow non-local connections, you need to add more
  76. # "host" records.  In that case you will also need to make PostgreSQL
  77. # listen on a non-local interface via the listen_addresses
  78. # configuration parameter, or via the -i or -h command line switches.
  79.  
  80.  
  81.  
  82.  
  83. # DO NOT DISABLE!
  84. # If you change this first entry you will need to make sure that the
  85. # database superuser can access the database using some other method.
  86. # Noninteractive access to all databases is required during automatic
  87. # maintenance (custom daily cronjobs, replication, and similar tasks).
  88. #
  89. # Database administrative login by Unix domain socket
  90. local   all             postgres                                peer
  91.  
  92. # TYPE  DATABASE        USER            ADDRESS                 METHOD
  93.  
  94. # "local" is for Unix domain socket connections only
  95. local   all             all                                     peer
  96. # IPv4 local connections:
  97. host    all             all             127.0.0.1/32            md5
  98. host    all             all             78.47.104.116/32           trust
  99. host    all             all             62.210.69.197/32           trust
  100. host    all             all             10.10.10.99/32           trust
  101.  
  102. # IPv6 local connections:
  103. host    all             all             ::1/128                 md5
  104. # Allow replication connections from localhost, by a user with the
  105. # replication privilege.
  106. #local   replication     postgres                                peer
  107. #host    replication     postgres        127.0.0.1/32            md5
  108. #host    replication     postgres        ::1/128                 md5
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement