[–] 1 point 8 hours ago* (1 child)

Because of this discussion (and because I hadn't looked at passkeys for quite a while), I did some testing...

And passkeys integrate seamlessly into my keepassXC to get backed up with all my regular passwords. So software- instead of device-based passkeys that can be properly transfered, synced or backed up work...

The problem is that tech-minded people that use password managers and think about security and backups are not the primary target group that passkeys should protect from every-day phishing attempts in the first place. And when it's supposed to protect the common user effectively and conveniently/frictionless but then instantly destroys the effect by advising to set up another login method it makes no sense.

  • source
  • parent
  • context
  • [–] 1 point 13 hours ago (2 children)

    Weder sollte gegen die Regierung klagen müssen das normale Vorgehen sein, noch sind derartige Klagen sonderlich erfolgreich. Wie oft wurde beispielsweise jetzt schon gerichtlich festgestellt, dass unser Innenminister rechtswidrig handelt, und wie viel hat das noch gleich an den illegalen Grenzkontrollen geändert?

  • source
  • parent
  • context
  • [–] 2 points 13 hours ago

    Yes I can backup a software one. But that's not the point. Passkeys are advertised as the future for common people as they eliminate the biggest issues: phishing.

    But then they don't advise people to use software passkeys, back them up and keep them save. Instead they tell them to configure an alternative/recovery login alongside the passkey should it be lost or damaged.

    They take a security feature, instantly remove the additional security and make it into a "you don't need to remember and type your password"-convenience thing. Yeah, great. A password manager could've already provided that convenience.

    So in the end those more technically-minded that will look at this and decide to use a software passkey so they can back it up will get some additional security they need much less (they are not the primary target group for phishing), and some convenience they already had (because they are already using a password manager).

    Passkeys aren't controversial because they are bad. They aren't. They are controversial because the actual way they are used makes zero sense for the purpose of added security. Which raises the question what the actual goal is.

  • source
  • parent
  • context
  • [–] 6 points 13 hours ago

    Passkeys are a good idea to prevent phishing. Using passkeys but then require a second method to login as a backup to prevent lockout when you lose your key (as many sites do) is epic bullshit. It makes an actual security improvement into some convenience feature so people don't need to remember/type passwords anymore. Because the phishing will now ask for the alternative/recovery login to fix some alleged problem with your account/passkey...

    So it suddenly does not provide additional security anymore above what a password manager would already do.

    When you sell somehting as a security feature then instantly defeat the additional security to make it just about convenience the question about the actual goal feels natural...

  • source
  • parent
  • context
  • [–] 9 points 13 hours ago* (3 children)

    It's mainly controversial because the actual use contradicts its purpose. Passkeys are phishing-resistent, which is still the main risk for password in real world scenarios, and are a good idea.

    But the websites supporting it put out big warnings when you don't have another method to login configured. And they don't actually advise you how to backup your passkey and keep it safe, but instead want you to set up an alternative way to login or recover your account. Which totally defeats the purpose in the first place.

    Quite the contrary: "there is a problem with your passkey/account, please use the recovery method you set up" even makes for more convincing phishing. So why are they pushing for passkeys when it isn't for security reasons?

  • source
  • parent
  • context
  • [–] 4 points 13 hours ago

    A passkey is cryptographically signed by the server when it's created.

    So it does not only has your credentials encrypted which are then used to login to a server, but it also carries information about the server and only that server can request the credentials from the passkey. So unlike a password a passkey is resistent to phishing attempts as you can't actually give your credentials away to anyone but the actual server it was created for.

  • source
  • parent
  • context
  • [–] 3 points 18 hours ago* (2 children)

    Passkeys fix a different problem.

    In my eyes the problem is that passkeys do not fix a problem. They just shift it to another layer...

    I can backup a password however I like. I can backup a TOTP authenticator (or specifically the secret that works with every one of them) however I like.
    I can not however backup a hardware device with my passkey.

    And the websites supporting passkeys obviously know it and explicitly warn when you don't have an alternative way of logging in configured as it's possible that simple hardware damage or loss locks you out of your account. Thus the "fix for a problem" is now relegated to a shiny new way of conveniently pressing the button on a key instead of typing and remembering passwords, while the actual attack surface is still there but now sitting in alternative login/account recovery instead.

  • source
  • parent
  • context
  • [–] 3 points 18 hours ago (4 children)

    Was meinst du mit "sehen"? Die orientieren sich nicht an der EU-Entwicklung, sondern sind die treibende Kraft dahinter. Und da nicht erst seit gestern, sondern spätestens seit Zensursula nach dem Scheitern ihrer Zensur- und Überwachungsphantasien hier zu lande, an die EU weitergereicht wurde, um dort das selbe nochmal zu versuchen.

  • source
  • parent
  • context
  •  

    As this will -thanks to me being quite clueless- be a very open question I will start with the setup:

    One nginx server on an old Raspi getting ports 80 and 443 routed from the access point and serving several pages as well as some reverse proxies for other sevices.

    So a (very simplified) nginx server-block that looks like this:

    # serve stuff internally (without a hostname) via http
    server {
    	listen 80 default_server;
    	http2 on;
    	server_name _; 
    	location / {
    		proxy_pass http://localhost:5555/;
                    \# that's where all actual stuff is located
    	}
    }
    # reroute http traffic with hostname to https
    server {
    	listen 80;
    	http2 on;
    	server_name server_a.bla;
    	location / {
    		return 301 https://$host$request_uri;
    	}
    }
    server {
    	listen 443 ssl default_server;
    	http2 on;
    	server_name server_a.bla;
       	ssl_certificate     A_fullchain.pem;
        	ssl_certificate_key A_privkey.pem;
    	location / {
    		proxy_pass http://localhost:5555/;
    	}
    }
    #actual content here...
    server {
    	listen 5555;
    	http2 on;
        	root /srv/http;
    	location / {
            	index index.html;
       	} 
        	location = /page1 {
    		return 301 page1.html;
    	}
        	location = /page2 {
    		return 301 page2.html;
    	}
            #reverse proxy for an example webdav server 
    	location /dav/ {
    		proxy_pass        http://localhost:6666/;
    	}
    }
    

    Which works well.

    And intuitively it looked like putting Anubis into the chain should be simple. Just point the proxy_pass (and the required headers) in the "port 443"-section to Anubis and set it to pass along to localhost:5555 again.

    Which really worked just as expected... but only for server_a.bla, server_a.bla/page1 or server_a.bla/page2.

    server_a.bla/dav just hangs and hangs, to then time out, seemingly trying to open server_a.bla:6666/dav.

    So long story short...

    How does proxy_pass actually work that the first setup works, yet the second breaks? How does a call for localhost:6666 (already behind earlier proxy passes in both cases) somehow end up querying the hostname instead?

    And what do I need to configure -or what information/header do I need to pass on- to keep the internal communication intact?

    view more: next ›