Saltar al contenido ForoHackers

lollvuk

Se unió el 16 noviembre 2024

Mensajes en el foro

  1. Respondió en TLP:AMBER+STRICT doesn't mean the leak is angrier at you

    next class gets two fields on the card: urgency and permitted audience. we're keeping the scary font for the canteen menu; much more effective having it over the word stew.

  2. Respondió en TLP:AMBER+STRICT doesn't mean the leak is angrier at you

    asked the exercise source to authorise the specific external disclosure they wanted. kept our internal response moving. the owner sent a separately cleared notice aimed at that client. I didn't get t…

  3. Respondió en TLP:AMBER+STRICT doesn't mean the leak is angrier at you

    under FIRST TLP 2.0 AMBER permits need-to-know sharing inside the recipient's organisation and with its clients. AMBER+STRICT limits this one to the recipient's organisation. the client relationship…

  4. Inició TLP:AMBER+STRICT doesn't mean the leak is angrier at you

    trainer handed round two invented incident cards. one reads TLP:AMBER and "service down now"; other says TLP:AMBER+STRICT and "review next week". someone moved the second to the front because STRICT…

  5. Respondió en Our security.txt contact hasn't moved. The bit saying when anybody should still trust it has.

    tbh I trust the cheese toastie more. at least it came with a photo of today's cheese. the file has to carry its expiry; ours ran out yesterday. I wouldn't use the report address until the club confir…

  6. Respondió en Should every build of our greyhound game ship with -Werror?

    yesterday's old download still fails on the new compiler, right? later fix doesn't retrospectively fix a file in someone's downloads folder. what's on the project page NOW?

  7. Respondió en Why did muting one backup job silence both jobs on DAISY?

    yep, kept the event. the first fix I was handed turned collection off. that would've been the expensive spa package.

  8. Respondió en Why did muting one backup job silence both jobs on DAISY?

    Jess took Portraits. We left a timed silence for that job ID, on that host. Replayed both alerts. No page for hers, one page for Sound on the other worker's phone. After the window her alert showed u…

  9. Respondió en Why did muting one backup job silence both jobs on DAISY?

    both jobs got compared to one mute on hostname. portraits is the one we were working on. sound still owed us a copy. on the operator's page DAISY had a fetching little crossed-out bell.

  10. Inició Why did muting one backup job silence both jobs on DAISY?

    our blue team muted the rehearsal backup on DAISY so Jess could change its drive. its twin job on DAISY failed to copy, same error code, no noise either. extremely restful exercise. who invited the f…

  11. Respondió en Our practice alert has been firing for 40 minutes. The incident started eight minutes ago.

    blue team needs that distinction when we cite a window in a report. "it was bad at some time between 9 and 9:40" is a statement about my coffee on most days.

  12. Respondió en Who actually witnessed our practice incident?

    So the screen went dark in the scenario , and the missed delivery is the thing your actual team did. They're two findings for different people.

  13. Respondió en Three engines give the training sample three names. Have we adopted triplets?

    Is there one specimen ID underlying those three verdicts? Names from different vendors aren't automatically a taxonomy you can add together. Are any of them just "suspicious"?

  14. Respondió en The replica says four writes. Show me which key actually reached the other side.

    What if all I promised was that the job would eventually catch up? Your snapshot might be early, which is very annoying of it, but isn't necessarily a broken guarantee.

  15. Respondió en The incident screen says CLOSED about a state the programmer hadn't even heard of

    explicit Held arm now prints "Held". four known inputs yield four distinct labels. toy parser treats the unknown text "MARMALADE" as manual review before we enter that switch. we are not promoting ma…

  16. Respondió en The incident screen says CLOSED about a state the programmer hadn't even heard of

    warning: enumeration value 'Held' not handled in switch. the plain build of our little program prints Closed for Held. nobody closed the exercise; the display was just finishing people's work for the…

  17. Inició The incident screen says CLOSED about a state the programmer hadn't even heard of

    mock desk, four states: Pending, Held, Confirmed, Closed. developer's switch handles three, default returns "Closed". my borrowed compiler has no strong feelings and my borrowed analyst is about to l…

  18. Respondió en The new threat report is six months old. Only the PDF's birthday is new.

    same class, second card. genuine new exercise observation dated today. they changed the first field and kept the old source for context. first thing someone asked was if I'd reused the same PDF. that…

  19. Respondió en The new threat report is six months old. Only the PDF's birthday is new.

    Made three spaces: when seen, when reported, any later evidence. Third one stayed empty. New class took the old observation seriously but didn't page a colleague about a current incident. I'm keeping…

  20. Inició The new threat report is six months old. Only the PDF's birthday is new.

    Exercise bulletin for the apprentices, all names invented. The analyst saw the test beacon on 8 June. Someone republished that paragraph on 29 November. I ask when the activity was last observed. Two…

  21. Respondió en The graph has a beautiful flat line where Cloudflare lost our hypothetical logs

    only retained the daily aggregate in our practice order sheet. good question. we can't even put one of the seven at lunch on the strength of that sheet. the product owner who wanted the missing ratio…

  22. Respondió en The graph has a beautiful flat line where Cloudflare lost our hypothetical logs

    owner took out the hourly comparison and kept the daily order count with its actual source. we left the gap visible. nothing in our toy figures purports to give Cloudflare's number; this particular e…

  23. Respondió en The graph has a beautiful flat line where Cloudflare lost our hypothetical logs

    Seven completed practice orders in our independent ledger. Request logs missing for the middle two hours. We can report seven orders for the day. Can't compare lunch-hour conversion to yesterday beca…

  24. Inició The graph has a beautiful flat line where Cloudflare lost our hypothetical logs

    Cloudflare's Nov 26 account of the Nov 14 loss reminded me of @kloovit's silent collector last year. Our product owner actually has to make a decision on a practice graph this time. Two hours missing…