Keyoxide: https://keyoxide.org/70d44f48bd35a7657aa524b06712beeaaf48a9d6

  • 10 Posts
  • 13 Comments
Joined 2 years ago
Cake day: June 13th, 2023
  • tblFlip@pawb.socialtoFurry@pawb.social•Canvas 2025 is July 12 - Let's create something together!English
    2·
    6 days ago

    yeah, it is a lot easier to create a template once and be done with it. that said, i don’t think that making a template for a more scattered approach is the hard part. organizing and communicating to everyone what the latest revision of that template is would be

    with one big image (where everything is collected in one place) we would also have to quickly set a boundary around the entire design before anyone else starts to claim parts of it. focusing on one or two smaller designs instead could make the initial rush a good bit more survivable, while also allowing us to utilize space left in between other projects as the event progresses

  • tblFlip@pawb.socialtoFurry@pawb.social•*Permanently Deleted*English
    8·
    4 months ago

    oh boy… that was bound to happen sooner or later to be honest. almost anyone posting art to major platforms will have someone cross post that to e621 eventually and its really up to you if you are ok with that, or want to do something about it

    is that legal? can they do that?

    thats really much more of a question for a copyright lawyer (which im not), but that depends on the license of the art. unless stated otherwise and assuming that the work is even copyrightable, everything is usually all rights reserved, which (as far as i know) does make redistribution illegal in most jurisdictions. if it was licensed as CC-BY for example, this post should be ok since you are listed as the artist and have links back to your profile and the post itself

    but thats the neat part! copyright rarely stops people from distributing art and memes

    why is my art there if i don’t even like the 18+ stuff

    for all kinds of reasons… for me (when i get bored enough) its always a “the archive must grow” kind of deal. there is this sort of desire to have everything nicely tagged and uploaded in one massive archive. it doesnt really have anything to do with being 18+ or not. there is lots of non-18+ artwork on there as well, but we all know thats not what people think of first. if anything, someone saw your art somewhere and thought it should be added to e6 so others can see it too. i dont think that the uploader had any ill intentions. they probably didnt even think that you might have reservations since youre not listed as DNP

    i know there’s a takedown form

    nice! have you also seen the DNP list? sending a takedown request will affect one post iirc, getting added to DNP goes a bit farther. getting added to DNP will either deny anyone from uploading your art, or will only allow certain uploads under certain conditions. for example you might be able to request that only original artwork without edits is posted

    hope that semi-infodump gives at least some answers :D

  • tblFlip@pawb.socialtoFurry Technologists@pawb.social•In a first, cryptographic keys protecting SSH connections stolen in new attack | Ars Technica
    0·
    2 years ago

    ok, after reading that article fully, it does sound a lot less concerning than the headline would like me to believe. it is early in the morning (almost 13:00) and this is a great chance to expose how little i know about all that, so i will:

    They believed SSH traffic was immune […].

    classic. we always think that something is perfectly safe until it breaks. also, looking at the article, the issue with RSA has been known since 1996. there had to be a useful application for this. such as TLS. and now some SSH implementations.

    Last year, researchers found that […] they were still able to passively observe faulty signatures that allowed them to compromise the RSA keys of […] Baidu.com

    no idea how this adds any value in a discussion about SSH, but i chuckled.
    now the article also get to some more interesting stats.

    5.2 billion SSH records. of that 590k with invalid signatures and 4.9k revealed factorization for a total of 189 unique private keys.

    now i would very much prefer that last number to be a solid zero, but out of 590k faults, only 4.9k were usable for the attack. everyone that thinks “oh thats nothing. im safe.” is still a fool, but it could be far worse. especially since this only target RSA and leaves ed25519 (and others) untouched.

    but it just gets even better:

    The researchers traced the keys they compromised to devices that used custom, closed-source SSH implementations that didn’t implement the countermeasures found in OpenSSH and other widely used open source code libraries.

    if i was drinking something reading this, i would have spat it out laughing. i am that kind of fun at parties. this also partially explains why there are “only” 590k invalid signatures in over 5.2 billion records total. and judging by how good some companies and organizations handle updates (assuming there will be updates from cisco, zyxel, hillstone and mocana), this will still be enough to be used in some attacks five years from now.