adds whitelist functionality

This commit is contained in:
Kyep
2019-05-10 09:54:20 -07:00
parent db950117ff
commit f4de59a4f8
11 changed files with 122 additions and 9 deletions
+12
View File
@@ -549,3 +549,15 @@ CREATE TABLE `ipintel` (
PRIMARY KEY ( `ip` )
) ENGINE = INNODB;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Table structure for table `vpn_whitelist`
--
DROP TABLE IF EXISTS `vpn_whitelist`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `vpn_whitelist` (
`ckey` VARCHAR(32) NOT NULL,
`reason` text
PRIMARY KEY (`ckey`)
) ENGINE=INNODB;
+13 -1
View File
@@ -547,4 +547,16 @@ CREATE TABLE `SS13_ipintel` (
`intel` REAL NOT NULL DEFAULT '0',
PRIMARY KEY ( `ip` )
) ENGINE = INNODB;
/*!40101 SET character_set_client = @saved_cs_client */;
/*!40101 SET character_set_client = @saved_cs_client */;
--
-- Table structure for table `SS13_vpn_whitelist`
--
DROP TABLE IF EXISTS `SS13_vpn_whitelist`;
/*!40101 SET @saved_cs_client = @@character_set_client */;
/*!40101 SET character_set_client = utf8 */;
CREATE TABLE `SS13_vpn_whitelist` (
`ckey` VARCHAR(32) NOT NULL,
`reason` text,
PRIMARY KEY (`ckey`)
) ENGINE=INNODB;
+9 -1
View File
@@ -1,8 +1,16 @@
#Updating the SQL from version 5 to version 6. -Kyep
#Creating a table to track the results of VPN/proxy lookups for IPs
CREATE TABLE `ipintel` (
`ip` INT UNSIGNED NOT NULL ,
`date` TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP NOT NULL ,
`intel` REAL NOT NULL DEFAULT '0',
PRIMARY KEY ( `ip` )
) ENGINE = INNODB;
) ENGINE = INNODB;
#Creating a table to track which ckeys are whitelisted for use of VPNs
CREATE TABLE `vpn_whitelist` (
`ckey` VARCHAR(32) NOT NULL,
`reason` text,
PRIMARY KEY (`ckey`)
) ENGINE=INNODB;