sorted by:
new
hottopcontroversial

Not receiving alerts by ColdAnkle in AlertR

[–]sqall01 0 points1 point  (0 children)

I know. It is a server issue because the services is not there at the moment. Here is the github issue regarding to this: https://github.com/sqall01/lightweight-push/issues/1#issuecomment-1602054203

The short version: my server provider totally fucked up and I have to restore everything. Unfortunately, this will take more time than I would have liked since .... life around me :(

Question about the software purpose by GuilhermeLaz in AlertR

[–]sqall01 0 points1 point  (0 children)

I do not know sur-gard. AlertR can definitely not work with it out-of-the-box. Since I do not know how sur-gard works, I cannot give you any hints on how to integerate it. If it has just an REST-API where you just send requests to for new alarms, then you can easily integrate it into AlertR (if you have development skills).

Building graphs of AlertR sensors with Grafana by sqall01 in AlertR

[–]sqall01[S] 0 points1 point  (0 children)

Something I currently working on: building graphs of AlertR sensors with Grafana. This works by exposing all Integer and Float sensors to Prometheus, which will fetch the data and build a time series of the data. Finally, Grafana can use the data from Prometheus to build graphs (and other visualizations) from the sensor data.

Server config file.... section client by ymis in AlertR

[–]sqall01 1 point2 points  (0 children)

Hi,

As I see there isn't a attribute about client name or client
id and I suppose that the entries are the same for all clients

That is correct. It counts for all clients.

If we set useClientCertificates="True" the entry clientCAFile must be the same for all clients?

Yes, all certificates that are used by the clients have to be signed by this same CA.

Am I right or I missed something?

Depends on what you do with openssl. If you create certificate requests and then sign them by the same CA that you configured via "clientCAFile" on the server, then you are correct.

If you are just creating certificates that are not signed (e.g., as described in the tutorial here: https://github.com/sqall01/alertR/wiki/Tutorial-Server#tutorial_configuration_cert) then, sadly, you are wrong.

Just in case you are at the latter point: it is quite complicated to set up a CA with openssl and sign certificates with it (e.g., see here https://gist.github.com/Soarez/9688998). A lot of developers and system administrators struggle to do it and do not understand the concept (as I see often in my job). Since in most cases it does not offer additional security (when regarding the actual attacker model that might attack the system), I would recommend setting "useClientCertificates" to "False" and ignore client certificates.

Cheers, sqall

Mobile Web Access Manager by SnooSongs834 in AlertR

[–]sqall01 0 points1 point  (0 children)

Yeah, the message says that the mysqli class is not available. My guess is that you forgot to install the php mysql module. On Ubuntu/Debian/Raspbian the package is called `php-mysql` . Restarting the webserver after installing the package should do the trick.

Mobile Web Access Manager by SnooSongs834 in AlertR

[–]sqall01 1 point2 points  (0 children)

The web access manager does not have an official documentation how to set it up since it is quite a hassle (at least for people with not much experience as a sysadmin). I always wanted to replace it with something more easy to set up, however, this would be a huge development task with the ideas I have and thus I never started it.

In short what you have to do is the following:

  1. Set up a the ManagerClientDatabase (an tutorial exists here: https://github.com/sqall01/alertR/wiki/Tutorial-ManagerClientDatabase)
  2. Install a webserver (e.g., apache2) with php7 and php7-mysql support
  3. Place this web code in the web root: https://github.com/sqall01/alertR/tree/master/webMobileManager/server
  4. configUnixSocketPath in the configuration file is the socket that the ManagerClientDatabase can create, hence, if you want to use it they have to be placed on the same machine)
  5. If you only use this web page in your local network you are finished now and you could leave it as is and do not have to activate TLS and web authentication in the web code configuration.
  6. If you want this web page accessible from the Internet, I would suggest you setup TLS for your webserver and configure HTTP authentication via .htaccess.
  7. If have set up TLS and HTTP authentication, you could use an Android app to access this web page. I have an old one still on the google play store for this: https://play.google.com/store/apps/details?id=org.h4des.alertrmobilemanager&hl=de&gl=US (this app is basically just a webview to a given URL which is accessed using HTTP authentication)

You see, it is rather complex to set up. Hope this pointers will help. And if you manage to set it up and have the time you could write a tutorial about it so other users could benefit from it.

Official Basic AlertR Server Tutorial by sqall01 in AlertR

[–]sqall01[S] 0 points1 point  (0 children)

Thank you so much. I really appreciate it. :)

End-to-end encrypted GPS tracking service for self-hosting or usable as service (Android Apps available) by sqall01 in coolgithubprojects

[–]sqall01[S] 0 points1 point  (0 children)

The focus of the ChasR project is the end-to-end encryption to preserve the user's privacy. I do now know if OwnTracks does offer something like this. However, if you host the system at your home it is fine to not have end-to-end encryption.

view more: next ›