locating-ssh-hackers | DIY project to show failed ssh login attempts
kandi X-RAY | locating-ssh-hackers Summary
kandi X-RAY | locating-ssh-hackers Summary
locating-ssh-hackers is a JavaScript library. locating-ssh-hackers has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.
A DIY project to show failed ssh login attempts on a map in real-time
A DIY project to show failed ssh login attempts on a map in real-time
Support
Quality
Security
License
Reuse
Support
locating-ssh-hackers has a low active ecosystem.
It has 11 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
There are 0 open issues and 1 have been closed. On average issues are closed in 41 days. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of locating-ssh-hackers is current.
Quality
locating-ssh-hackers has 0 bugs and 0 code smells.
Security
locating-ssh-hackers has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
locating-ssh-hackers code analysis shows 0 unresolved vulnerabilities.
There are 0 security hotspots that need review.
License
locating-ssh-hackers is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
locating-ssh-hackers releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of locating-ssh-hackers
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of locating-ssh-hackers
locating-ssh-hackers Key Features
No Key Features are available at this moment for locating-ssh-hackers.
locating-ssh-hackers Examples and Code Snippets
No Code Snippets are available at this moment for locating-ssh-hackers.
Community Discussions
No Community Discussions are available at this moment for locating-ssh-hackers.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install locating-ssh-hackers
The setup of influxdb is pretty straignt forward: we will not expose influxdb to the network (because we don't need this in this use-case). We will be using helm as the package manager to do the install, based on a slightly modified values.yml. The influxdb user is admin and you can retrieve the auto-generated password with: kubectl -n influxdb get secret influxdb-influxdb-auth -o jsonpath="{.data.influxdb-password}" | base64 -d.
We will use helm to setup grafana as well:.
let helm create the ingress by setting ingress.enabled to true in values/grafana/values.yaml
Deploy an own ingress: this is the way I prefer to do things because I use traefik as an ingress controller on my kubernetes cluster, that takes care of generating Let's Encrypt certificates automatically for any new ingress. Aside from that I did not want to expose grafana to the internet so I added a whitelist-source-range definition to the ingress to make sure that grafana only accepts incoming traffic coming from my local network.
Edit the hostname in manifests/grafana/ingress.yaml
Deploy the ingress: kubectl -n grafana apply -f manifests/grafana/ingress.yaml
The log receiver is a tcp socket listener written in nodejs that will get called from rsyslogd.
Build the container: docker build -t <your-dockerhub-name>/logincollector:<tag>
Push the container: docker push <your-dockerhub-name>/logincollector:<tag>
Change the deployment in manifests/logincollector/deployment.yaml according to your docker image
Create the namespace: kubectl create ns logincollector
Deploy: kubectl -n logincollector apply -f manifests/logincollector/
Finally we will setup the dashboard in grafana:.
Create a new dashboard names "Login Attempts"
Add the World panel and edit it
Go to [General] and edit the title: "Failed Login Attempts"
Go to [Metric] and add "InfluxDB" as datasource
Edit the query to be SELECT "value" AS "metric" FROM "login-attempts".."geossh" WHERE $timeFilter GROUP BY "geohash"
Set the format to Table
Go to [Worldmap] and edit the visual options to suit your needs (defaults are fine as well)
In "Map data options" set "Location data" to geohash, "Geohash field" to geohash, "Metric field" to metric
We will use helm to setup grafana as well:.
let helm create the ingress by setting ingress.enabled to true in values/grafana/values.yaml
Deploy an own ingress: this is the way I prefer to do things because I use traefik as an ingress controller on my kubernetes cluster, that takes care of generating Let's Encrypt certificates automatically for any new ingress. Aside from that I did not want to expose grafana to the internet so I added a whitelist-source-range definition to the ingress to make sure that grafana only accepts incoming traffic coming from my local network.
Edit the hostname in manifests/grafana/ingress.yaml
Deploy the ingress: kubectl -n grafana apply -f manifests/grafana/ingress.yaml
The log receiver is a tcp socket listener written in nodejs that will get called from rsyslogd.
Build the container: docker build -t <your-dockerhub-name>/logincollector:<tag>
Push the container: docker push <your-dockerhub-name>/logincollector:<tag>
Change the deployment in manifests/logincollector/deployment.yaml according to your docker image
Create the namespace: kubectl create ns logincollector
Deploy: kubectl -n logincollector apply -f manifests/logincollector/
Finally we will setup the dashboard in grafana:.
Create a new dashboard names "Login Attempts"
Add the World panel and edit it
Go to [General] and edit the title: "Failed Login Attempts"
Go to [Metric] and add "InfluxDB" as datasource
Edit the query to be SELECT "value" AS "metric" FROM "login-attempts".."geossh" WHERE $timeFilter GROUP BY "geohash"
Set the format to Table
Go to [Worldmap] and edit the visual options to suit your needs (defaults are fine as well)
In "Map data options" set "Location data" to geohash, "Geohash field" to geohash, "Metric field" to metric
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page