• 0 Posts
  • 134 Comments
Joined 3 years ago
cake
Cake day: August 2nd, 2023

help-circle
  • When connected to your internal network, what is the results of:

    nslookup sub.domain.tld AGH.IP.Address

    This should respond authoritative with the IP you need to access NPM’s VIP IP address. If that is not the case, let us see your AGH configuration for your sub.domain.tld.

    If that does return the correct IP, verify that it responds to https using curl on Linux or windows (replace curl with curl.exe)

    curl -vvvI https://sub.domain.tld/

    If this is not connecting or showing a cert error then there’s a misconfiguration on the NPM side. Screenshots of your site configuration for one of the sites would be helpful. The domain name should match sub.domain.tld (not your duckdns) and be bound to the let’s encrypt cert.





  • Instead of a default gateway you can configure just your VPN IP address to go to your gateway. You might also need DNS servers depending on your setup.

    Example: ip route add 1.1.1.1/32 via 192.168.1.1 dev eth0

    Note that without a script this may be flaky if you’re using DNS to resolve the VPN. It might be better to have a script that resolves the IP(s) of the VPN and then adds routes.

    That being said, your VPN software is usually designed to install routes that have higher priority so that they will get used before the local network. One such way is by adding half-internet routes (0.0.0.0/1 and 128.0.0.0/1) which get preferred over the larger default route. If you run ip route once connected you may see those routes present.

    While I’m not sure if it works in rootless, take a look at binhex/arch-delugevpn project which has scripts to set up a similar network isolation environment.













  • One thing not mentioned is that modern password hashing algorithms will iterate your password hundred of thousand of times. This makes cracking the hash much more time intensive. For example if 1 hash takes 1ms (most hash algorithms are way quicker), then 1000 iterations of that means it will take 1 second to compute your hash from the input. The server has to spend that time to validate your password when you login, but that’s a small tradeoff to make brute force attempts which will now have to calculate 1000x hashes for each input.

    We updated to the NIST recommendation of 600000 iterations a few years ago when it was released, with regular increases every year. Logins take upwards of 5 seconds but it’s added security in the event the data is leaked.