• 0 Posts
  • 18 Comments
Joined 2 years ago
cake
Cake day: June 23rd, 2023

help-circle





  • PowerCrazy@lemmy.mltoProgrammer Humor@lemmy.mlA quick intro to pointers
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    3 months ago

    I “understood” on a basic level what pointers were when i was first learning programing as a 12-13year old. But I never understood HOW to use them, or manipulate them, or what functions you use to interact with them, or how to examine them, or how to declare them, etc etc. And since I was young I never got the opportunity to take an actual programming class that taught any of that throughout high school. By the time I got to college I went with Electrical Engineering instead of computer science and so my journey with pointers ended.

    Now I do python and never have to think about pointers.


  • This is fundamentally true. However it is possible to limit the bandwidth of data the employee can exfiltrate.

    Assuming a privileged employee suddenly becomes a bad actor. Private-keys/certs are compromised, any kind of shared password/login is compromised.

    In my case I have a legit access to my company’s web-certs as well as service account ssh-key’s, etc. If I were determined to undermine my company, I could absolutely get access to our HSM-stored software signing keys too. Or more accurately I’d be able to use that key to compile and sign an arbitrary binary at least once.

    But I couldn’t for example download our entire customer database, I could get a specific record, I could maybe social engineer access to all the records of a specific customer, but there is no way I’d be able to extract all of our customers via an analog loophole or any standard way. The data set is too big.

    I also wouldn’t be able to download our companies software source code in it’s entirety. Obviously I could intelligently pick a few key modules etc, but the whole thing would be impossible.

    And this is what you are trying to limit. If you trust your employees (some you have to), you can’t stop them from copying the keys to the kingdom, but you can limit the damage that they can do, and also ensure they can’t copy ALL the crown jewels.




  • I’m a network engineer and I run ipv6 natively in all of our datacenters. There are even a handful of end systems that have ipv6 native networking stacks with ipv4 sockets for our non-ipv6 compatible applications. IPv6 issues are basically self-inflicted at this point by companies that see their IT systems as cost centers, or by basilisk directors who’s knowledge stopped in the 90’s.


  • PowerCrazy@lemmy.mltoLinux@lemmy.mlSSH as a sudo replacement
    link
    fedilink
    English
    arrow-up
    25
    ·
    edit-2
    8 months ago

    Seems novel. But from a security aspect, if OpenSSH has security vulnerability that allows an unauthenticated user to login, via whatever means, once you are in the system as a non-privileged user, you are now free to use the same vulnerability to get root.

    Basically this exercise is like using two locks that have the same key to open them. If the same key opens them, then a weakness in one, is now a weakness in the other so why bother with two identical locks?




  • PowerCrazy@lemmy.mltoLinux@lemmy.mlHow terminal works
    link
    fedilink
    English
    arrow-up
    8
    ·
    9 months ago

    hahaah. Ok sure you win. Linux TTY’s are absolutely not terminals. Sure they are called terminals, they are for all intents and purposes modern-day terminals with a long and storied history that directly links them to terminals from the 70’s but since they aren’t a physical piece of hardware that electro-mechanically connects to a mainframe, obviously they aren’t really terminals and they should be be called something else.




  • Self-approval leads to a road of sadness. For example, a theoretical company needs to self-renew an ssl cert. No problem, the cert will be stored with the rest of the secrets and retrieved in a secure way on deployment. Unfortunately if you don’t store the cert key in a secure way, the deployment still works fine and you don’t need to figure out the “onerous” encryption process.

    So you push the private key to the company git repo, and then deploy the cert! Done and Done.