[–] 3 points 6 months ago (1 child)

If it game from their app theres not much you can do besides go grab the latest from their site yourself. I would say fuck it. My gaming computer only has games on it.

  • source
  • [–] 2 points 6 months ago (1 child)

    Wonderful day!

    I am sorry, but considering your quite exquisite name, it feels like you searched for Communities already!
    Yet, feeling your appreciated interest in the marvelous programming language, have you checked out more focused Communities?:
    - !c_lang@programming.dev
    - !cpp@programming.dev
    - !programming@programming.dev

    I'd definitely recommend the following book, too!:
    - https://amazon.com/dp/0131103628 ("C Programming Language, 2nd Edition"... by Brian W. Kernighan and Dennis M. Ritchie...)

  • source
  • [–] 4 points 6 months ago (1 child)

    The first char appears because your terminal is echoing back what you are typing in. This is the default, and you see it also in most other programs, with password inputs as a big exception. Those tell the terminal in some way that it should disable the echo functionality, and turn it back on after the password has been read. see https://stackoverflow.com/questions/59922972/how-to-stop-echo-in-terminal-using-c for more info

  • source
  • [–] 2 points 6 months ago*

    Setting up firewalls on the individual hosts on your network is good, but the "main" firewall is always the box that does the NAT between LAN and WAN! Assuming you're not running a full IPv6 stack that is, in which case you'd be right to make policies for each device. But for IPv4, your OpenWRT router is what gets hit when someone tries to open a connection to your public IP. Packets can get into your LAN because of a handful of reasons:

    • It is a response packet to a LAN-initiated connection
    • There is an explicit input rule
    • There is an explicit forwarding rule
    • A client has created a port forwarding via UPnP, if allowed

    All of these happen on the router, the individual host's firewalls only ever see packets if the router first sends them their way (again, unless IPv6, sort of), or if the packet originated from another host within the LAN.

    Now to actually answer your question, yes you need to allow DHCP to receive IP leases from your ISP. DHCP-Renew seems already like it's the client-side only so that's as restrictive as you can go. ICMPv6 is fundamental to IPv6 operation in general, and it needs to be forwarded because IPv6 removes the concept of NAT and gives more autonomy to each endpoint - forwarding the ping request (and other "network configuration" packets) directly to the endpoints. Whether to respond to ICMPv4 pings on WAN or not is pretty much personal preference for a residential setup, personally I don't.

    If you are still learning networking in general, I would suggest disabling IPv6 and having fun in v4 land until you can find the time to properly study, test, and configure the whole network for it, which might be never - I still haven't fully enough to trust my smartphone and IoT shiz to have a globally-routable public address.

    Just to be clear, I want to clarify that the statement

    I guess the firewalls on my OpenWRT routers will serve non firewalled hosts, such as when I have friends over that connect to my network, and my own smartphones of course.

    Is incorrect but in different ways depending on what IP version the packet is. For IPv4, they will always go through the OpenWRT chains first, and if forwarded then it will hit the host. For IPv6, it will be forwarded directly to the host unless explicitly forbidden in the router's forward chain. That means that an ESP32 running whatever web interface bound on [::]:80 (v6 equivalent of 0.0.0.0:80) is now reachable by the internet. In both cases, the router has no way of knowing which endpoints are running a firewall and which don't, so they're treated the same.

  • source
  • [–] 4 points 6 months ago* (2 children)

    It doesn't improve any guarantees, it's strictly an opsec practice. By default you can publicly view the fingerprint of the public key(s) of the recipient(s) to aid in selecting the correct key for decryption, while --throw-keyids removes that metadata. Don't use it if you want to demonstrate that the message is not additionally encrypted to other keys, i.e. the conversation is confidential. Use it if you don't want a MitM to know who you're talking with.

  • source
  • parent
  • context
  • [–] [S] 2 points 6 months ago (3 children)

    Sorry for spamming. I just tried encrypting it with my own credentials as recipient. Worked like a charm. Thank you so much! :D

    By the way, is --throw-keyidsa countermeasure against man in the middle attacks? Does it assume that the recipient's private key has been compromised?

  • source
  • parent
  • context
  • [–] 8 points 6 months ago* (5 children)

    You need two if the message doesn't end with a newline AFAIK. This is the case for several tools that operate on stdin, but I'm unsure if it is a program thing or a bash thing.

    Sidenote, you can add yourself as a recipient too to be able to decrypt messages you send. I don't think it violates any principles or etiquette, and you can/should use --throw-keyids anyway

  • source
  • [–] 2 points 6 months ago

    Also, a lot of online logins have a cool down after an incorrect attempt, too many failed attempts and the account may lock from anywhere to a few mins (M$ is iirc 5 or 10 mins by default after 3 fails) to permanently locked

  • source
  • parent
  • context
  • [–] [S] 2 points 6 months ago* (last edited 6 months ago)

    Thanks! Great insight! Yeah, I didn't mean to say that the attacker knows the characteristics of the target's passwords. I meant to say, "let's assume that the attackers assumes..." Why any attacker every would assume anything is beyond the point, since I guess they wouldn't, haha. I'm sure seasoned hackers are methodical and empirical in their conquests.

  • source
  • parent
  • context
  • [–] 2 points 6 months ago (1 child)

    You're on a right track. But there's a ton of variance, for example poorly built systems (used even today) store passwords in plaintext, so then it doesn't matter how complex your password is, it can still be used as a 'seed' to crack better protected databases. And properly salted+hashed database doesn't have any indication which password is poor and which is strong, so (at least I assume so) attackers just keep their algorithms running for however many hours they think is needed/worth the time and just stop processing once they have sufficient payout of the attack.

    For example, without salting and using md5 hash 'password' gives hash '286755fad04869ca523320acce0dc6a4'. Using randomly generated 55 character password gives hash 'd1006257a2b09c76bcba82f209650056'. So, just a database with hashed passwords alone doesn't give you any information if the password is strong or weak.

  • source
  • parent
  • context
  • [–] 4 points 6 months ago (1 child)

    The attacker could brute force it. Or they can make a phishing page to try and get the user to enter in their password.

    1. An attacker would get a similar enough looking domain and mimic the target login page using something like EvilNginx
    2. The attacker would send a fake email to the victim while looking as legit as possible. Saying something like too many login attempts have been detected, please use this URL to confirm your account, or your password is expiring please use this URL to update it. That sort of thing.
    3. The victim would click the URL going to the attackers login page and enter in their details.
    4. The attacker now has the valid login credentials.
  • source
  • [–] [S] 4 points 6 months ago (5 children)

    Thanks! The answer I take with me from this, in regards to my question, is: an attacker wouldn't try to brute force secure passwords because of hardware limitations and that, typically, only insecure passwords are valuable targets for brute force attacks. Also, that going after information that is not viable for brute forcing requires social engineering.

  • source
  • parent
  • context
  • view more: ‹ prev next ›