Advertisement
Guest User

Untitled

a guest
Jun 6th, 2017
97
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.59 KB | None | 0 0
  1. #### PLEASE NOTE ##################################################
  2. # #
  3. # SECTIONS SURROUNDED BY "#"s ARE THERE TO EXPLAIN, IN DETAIL, #
  4. # WHAT EACH SETTING IS USED FOR. #
  5. # #
  6. # THE ACTUAL SECTION SETTINGS WILL FOLLOW SHORTLY AFTER EACH #
  7. # SETTING'S EXPLANATION. #
  8. # #
  9. ###################################################################
  10.  
  11. <Login
  12.  
  13. # Hostname or IP address the login server will listen on.
  14. # 0.0.0.0 will listen on all interfaces, so if you don't
  15. # know, leave it as default!
  16. host = "95.168.183.251"
  17.  
  18. # Port the login server listens on.
  19. # Default login server port: 15100
  20. port = "15100"
  21.  
  22. # Defines the level of content that will be shown.
  23. LogLevel = "2"
  24.  
  25. # Enable automated IP bans of potential "bad people"?
  26. # 0 = No (only if you have problems)
  27. # 1 = Yes
  28. AutoIPBanChecks="0"
  29.  
  30. # Defines the period of time (in minutes) between full account reloads.
  31. # An account will not exist after a player has registered until an
  32. # accounts reload has been performed.
  33. ReloadPeriod = "1"
  34.  
  35. # Use in-game news? To create news, use the "News Creator".
  36. # 0 = No
  37. # 1 = Yes
  38. UseIngameNews = "0"
  39.  
  40. # Hi there! You're reading the configuration.
  41. # Set Die to 0.
  42. Die="0"
  43.  
  44. # Enable auto-registration? (Registers an account on login if it does not exist)
  45. # 0 = No
  46. # 1 = Yes
  47. AutoRegister = "0"
  48.  
  49. # If auto-registration is enabled, and you have any required columns
  50. # (columns that do not have a default value or do not have "Allow nulls" ticked)
  51. # in TB_USER, you must specify them here as a continuation of the existing query:
  52. #
  53. # INSERT INTO TB_USER (strAccountID, strPassword<HERE>)
  54. # VALUES('user', 'pass'..);
  55. AutoRegisterExtraColumns = ", strSocNo, iDays"
  56.  
  57. # If auto-registration is enabled, and you have any required columns
  58. # (columns that do not have a default value or do not have "Allow nulls" ticked)
  59. # in TB_USER, you must specify their intended value here as a continuation of the
  60. # existing query:
  61. #
  62. # INSERT INTO TB_USER (strAccountID, strPassword..)
  63. # VALUES('user', 'pass'<HERE>);
  64. AutoRegisterExtraValues = ", 1234, 6"
  65.  
  66. # Use the new/1.310 server-list structure?
  67. # 0 = No (for servers prior to 1.310)
  68. # 1 = Yes (for 1.310 servers)
  69. NewServerList = "0">
  70.  
  71. <Billing
  72. Enabled = "1"
  73. host = "95.168.183.251"
  74. port = "15200">
  75.  
  76. <Database
  77.  
  78. # Your accounts database's datasource name
  79. # This is the entry in the ODBC configuration that you
  80. # have configured to point to the accounts database.
  81. #
  82. # If you are using a single database setup (ie: KN_online),
  83. # you'll use the DSN that points to your only database.
  84. #
  85. # If you're unsure, just keep it default and hope it works. :P
  86. dsn = "KN_online"
  87.  
  88. # The SQL username that has access to your accounts database.
  89. # Default setups use "knight", so if you're unsure, just
  90. # leave it as default and hope it works!
  91. user = "knightv"
  92.  
  93. # The password to the username above.
  94. # If unsure, please leave it default.
  95. pass = "114122889"
  96.  
  97. # There are two definitions for the VERSION table.
  98. # 0 = Uses shortened column names, ie: compname
  99. # 1 = Uses proper column names, ie: strCompressedName
  100. # The default applies to most setups.
  101. VersionTable = "0"
  102.  
  103. # Hi there! You're reading the configuration.
  104. # Set Die to 0.
  105. Die="0"
  106.  
  107. # Use a stored procedure to handle any custom stuff?
  108. # 0 = No
  109. # 1 = Yes
  110. # The login server already handles the login, so unless
  111. # you have any extreme need to call the stored procedure,
  112. # please leave it disabled!
  113. UseAccountLogin = "0"
  114.  
  115. # The name of the stored procedure used by the above config
  116. # option.
  117. StoredProcedureName = "ACCOUNT_LOGIN"
  118.  
  119. # Hash passwords from the client?
  120. # 0 = No
  121. # 1 = Yes
  122. HashPasswords = "1"
  123.  
  124. # Hash them using what?
  125. # - "md5": Uses the in-built MD5 hasher.
  126. # - "sha1": Uses the in-built SHA1 hasher.
  127. # - "custom": Calls a custom T-SQL function, configured below.
  128. HashType = "custom"
  129.  
  130. # If you are using the in-built MD5 or SHA1 hashers, you can
  131. # seed the password make things harder for hackers.
  132. # 0 = No
  133. # 1 = Yes
  134. SeedHashes = "0"
  135.  
  136. # If the above is enabled, specify the seed here.
  137. # %s is the password, it MUST be kept in there somewhere.
  138. # The surrounding text is the seed - you can move %s to any
  139. # location inside that string.
  140. HashSeed = "seed%shere">
  141.  
  142. <FTP
  143.  
  144. # 'URL' of the FTP server where the patches are hosted.
  145. # In ftp://ftp.your-site.net/abc/ the URL is ftp.your-site.net
  146. url = "lifeko.serveftp.com"
  147.  
  148.  
  149. # Relative path from the URL. Directory where the patches are.
  150. # In ftp://ftp.your-site.net/abc/ the path is /abc/
  151. path ="/">
  152.  
  153. #### PLEASE NOTE ##################################################
  154. # #
  155. # THIS SECTION SHOULD ONLY BE CONFIGURED IF "HashType" WAS SET TO #
  156. # "custom" IN THE DATABASE CONFIGURATION BLOCK! #
  157. # #
  158. # If you did not set it to "custom", then you may stop reading #
  159. # and save & close the configuration file! You are done! #
  160. # #
  161. # With that said... #
  162. # #
  163. # The hash function is called with the password as the first #
  164. # parameter. #
  165. # #
  166. # Each of the parameters below will be called consecutively, and #
  167. # only in that order. #
  168. # #
  169. # If your function differs, please change the order of the #
  170. # parameters in your T-SQL function to copy how they appear here. #
  171. # #
  172. # Order here: #
  173. # 1. strPasswd #
  174. # 2. strAccountID #
  175. # 3. strClientIP #
  176. # #
  177. # Example of a hash function #
  178. # This uses all parameters; you can disable account ID/IP below. #
  179. # #
  180. # CREATE FUNCTION MyHashFunc #
  181. # ( #
  182. # @strPasswd varchar(21), #
  183. # @strAccountID varchar(21), #
  184. # @strClientIP varchar(15) #
  185. # ) RETURNS VARCHAR(1024) #
  186. # AS #
  187. # #
  188. # You should also note that the maximum hash size is 1024 bytes, #
  189. # which should be more than enough for anybody! #
  190. # #
  191. ###################################################################
  192. <HashFunction
  193.  
  194. # Name of the T-SQL hash function you want to call.
  195. Name = "USER_LOGIN"
  196.  
  197. # Pass account ID to function?
  198. # 0 = No
  199. # 1 = Yes
  200. AccountName = "1"
  201.  
  202. # Pass client's IP address to function?
  203. # 0 = No
  204. # 1 = Yes
  205. IPAddress = "0">
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement