• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 25th, 2023

help-circle

  • variaatio@sopuli.xyztopics@lemmy.worldBehold
    link
    fedilink
    arrow-up
    10
    ·
    10 months ago

    There possibly is a pushers/braking truck attached to the rear of the Transporter.

    Also one must remember on transporter it is about winning over rolling resistance rather than the weight. Doesn’t necessarily take that powerfull truck on flat ground to pull even great load.

    Also turbine housing has lot of air and as equipment to be lifted to top of a mast, built with light weight in mind. Not for pulling it, but in thought of the crane that has to lift that thing dead load up.


  • variaatio@sopuli.xyztoMastodon@lemmy.mlGot to love Mastodon
    link
    fedilink
    arrow-up
    20
    arrow-down
    1
    ·
    edit-2
    1 year ago

    Since I is decentralized, it is upto the intances. There is no central authority to eject an instance. Rather other instances individually block the instances they find objectionable to their own criterion.

    At basic its that. Inpractice moderation federations and coalitions etc. have formed among instances of “we maintain joint blocking list and any of us can suggest new additions to it”.

    Due to this one can get ejected from rather sizeable swath, if one one the moderation federations puts one on block list and that is pretty much as far as an “you have 24 hours or we boot you”. You get booted from all the instances part of that federation/coalition.

    Plus stuff like just sources/authors trusted by various instances. “If this guy puts an instance on their published black list, we block. So far that guy has done good job with his list”. Ofcourse instance can at any point decide to not trust that list author anymore.

    So there is no one “how mastodon does it”. Infact this is the one area where “on what instance are you” matters. Since how your home instance decides to do moderation and blocking, that is how your blocking happens. Plus ones personal additions on top.

    Mastodon has a moderation action feature, where one can see listing of what instances and user have been blocked or other moderation action taken. There is explanation field there also for moderator to say “why” but obviously that is upto instance on what their policy is on how exacting their moderation documentation policy is.


  • Seems like a huge headache with stolen/lost phones, wonder how they handle revokation…

    Right maybe should have clarified that. The authentication is facilitated by the trusted middle party aka phone company.

    When you log in using this service, you tell using service your phone number. Well their contacted authentication handler (usually one of the phone operators), they forward the request to your operator, who knows to forward it to the phone (as I understand as a network service SMS, like how operators settings updates also get send to the SIM and phone), this service message is handed by the phone cellular interface to the SIM. SIM applet notices “oh this is authentication request”. It displays the session ID of authentication (generated at the original authentication session and displayed there also) and then asks to enter security code to approve (or decline the request)

    As such revocation is two fold. First your operator will list the certificate/key invalid. Secondly, since operator is handling the message passing anyway, they know to refuse to send the authentication requests in the first place to the compromised SIM. since as the SIM, that also defines where to send the requests. It is both the independent crypto validation, but also the cell network subscriber identity. Compromised sim stops getting any requests, since it is shutout from cellular connection. Can’t make calls, can’t send and receive texts, since the sim isn’t anymore tied to valid subscriber contact.

    Plus with crypto system there is always the option of official public revocation server. Which kind of system is what the national ID smart card system uses. Anyone accepting identifying by those signatures gets told “the official key/certificate/revocation server is this one. Regularly check it for listed revocations by the root trust authority”


  • i don’t agree that it keeps users locked in. convenience wise it should be alot easier with e-SIM, technically you should just be able to open up an app and install a new e-SIM and voila your on a new provider.

    As long as the phone maker and the phone service company play nice. The whole point of physical sims is. “you break your phone screen and phone? You can literally in the minute borrow your buddy’s phone, slap your sim in it”.

    Why would it matter? For example here in Finland we have this thing called The Mobile ID. Which is commercial high security identification method, that works on the SIM. It’s user interface is the phone, but the actually crypto and logging works on the SIM. Just as with PIN number, the phone is just keypad to tell the SIM the security code to unlock it and operate. Not only does it work on SIM, due to security it is tied to the SIM. Each ID is a cryptographic key living physically in the SIM. never to leave it. public-private key exchange between the authentication server and SIM. on first boot/activation, SIM generates in-situ the private key, sends the public key to phone company, normal registrations hand shakes. Only thing anyone else has is the publickey. they private key lives it’s live in the SIM and just on getting signatory request and then correct unlock PIN signs the request and sends it back.

    Which again means in the “oh my phone broke” situation means I haven’t lost my mobile ID. Just yank the SIM out of the husk of the broken flagship expensive smart phone and slap it into the cheapest 30 euro “I make calls and send text” budget phone. Still works just as well. Any phone you find (that isn’t SIM locked) will work, since as said the ID is the SIM, the phone is just keypad interface.

    Also physical external sim allows physical update of the crypto processor. with eSim, if there is hardware fault or vulnerability found with the eSim, you are toast. With physical sim? So sorry customer, there has been vulnerability wound with the Sim crypto. Do you come to visit nearest operator store to get your new sim for your phone or do you want it sent by mail. Specially on say long lasting equipment… It is a very good thing there is a physically exchangeable cryptographic component. Rest of the equipment isn’t toast, just because someone cracked the SIM crypto.