GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Sophie Schmieg (sophieschmieg@infosec.exchange), page 2

  1. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Wednesday, 22-Jan-2025 03:37:35 JST Sophie Schmieg Sophie Schmieg

    Frontpage News. Digital. Artist unknown.

    In conversation about 5 months ago from infosec.exchange permalink

    Attachments


    1. https://media.infosec.exchange/infosec.exchange/media_attachments/files/113/867/013/544/053/989/original/fec85f119a81ed55.png

    2. https://media.infosec.exchange/infosec.exchange/media_attachments/files/113/867/014/015/052/383/original/e1b7e58f50fd42cb.png
  2. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Saturday, 18-Jan-2025 04:27:17 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Dan Goodin
    • Femme Malheureuse

    @femme_mal @dangoodin why is American Express even a thing? I don't know any stores that support it, and this fees table kind of shows why.

    In conversation about 5 months ago from gnusocial.jp permalink
  3. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Friday, 17-Jan-2025 02:50:05 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Paul Cantrell
    • August

    @inthehands @august don't forget that in the case of using a web interface, you have no guarantees that the JavaScript sent to you is the same JavaScript that was sent to someone else, or even the same that was sent to you yesterday. So if you want to target an individual, you can just ship a special version of the code that includes a line saying "and now send the private key unencrypted to the NSA", and you're unlikely to ever notice.

    With downloaded apps such as signal (even signal desktop), this attack is far more difficult to pull off (but not mitigated fully if you want updates regularly)

    In conversation about 5 months ago from infosec.exchange permalink
  4. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Thursday, 16-Jan-2025 01:09:10 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • mekka okereke :verified:

    @mekkaokereke you famously cannot not communicate. And choosing not to listen, and walking away is the ultimate counterargument, that does not even need a word. It is a show of force, saying "your opinion isn't even important enough for me to respond", and they cannot abide by that. They need their words to define reality, and every indication that it doesn't needs to be destroyed.

    In conversation about 5 months ago from infosec.exchange permalink
  5. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Tuesday, 07-Jan-2025 07:47:54 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Lauren Weinstein

    @lauren so far, there is still no evidence of person to person transmission. So I think for the moment the pandemic part 2 risk is contained. Let's hope it stays that way.

    In conversation about 5 months ago from infosec.exchange permalink
  6. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Sunday, 05-Jan-2025 02:59:26 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Ryan Castellucci :nonbinary_flag:
    • David Chisnall (*Now with 50% more sarcasm!*)
    • Tableflip

    @david_chisnall @ryanc @Lookatableflip and don't forget the whole Debian random number generator debacle. That was probably one of the motivating factors for adding RDRAND and friends to modern CPUs.

    In conversation about 6 months ago from infosec.exchange permalink
  7. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Saturday, 04-Jan-2025 16:09:04 JST Sophie Schmieg Sophie Schmieg

    @ireneista technically Bas got this one. But I do get my fair share of cranks, and have been for a while, cryptography just has a very high crank density.

    In conversation about 6 months ago from infosec.exchange permalink
  8. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Saturday, 04-Jan-2025 12:13:27 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Paul Hoffman

    @paulehoffman oh yeah, he founded a company, apparently. It doesn't say if he actually found anyone dumb enough to invest in it, but yeah.

    Remember, it's only fraud if you actually understand that what you're doing is nonsense!

    In conversation about 6 months ago from infosec.exchange permalink
  9. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Saturday, 04-Jan-2025 12:00:08 JST Sophie Schmieg Sophie Schmieg
    in reply to

    In case you do not know how GenAI works, here is a very abridged description:
    First you train your model on some inputs. This is using some very fancy linear algebra, but can be seen as mostly being a regression of some sorts, i.e. a lower dimensional approximation of the input data.
    Once training is completed, you have your model predict the next token of your output. It will do so by creating a list of possible tokens, together with a rank of how good of a fit the model considers the specific token to be. You then randomly select from that list of tokens, with a bias to higher ranked tokens. How much bias your random choice has depends on the "temperature" parameter, with a higher temperature corresponding to a less biased, i.e. more random selection.

    Now obviously, this process consumes a lot of randomness, and the randomness does not need to be cryptographically secure, so you usually use a statistical random number generator like the Mersenne twister at this step.

    So when they write "using a Gen AI model to produce 'true' random numbers", what they're actually doing is using a cryptographically insecure random number generator and applying a bias to the random numbers generated, making it even less secure. It's amazing that someone can trick anyone into investing into that shit.

    In conversation about 6 months ago from infosec.exchange permalink

    Attachments


  10. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Saturday, 04-Jan-2025 07:38:04 JST Sophie Schmieg Sophie Schmieg

    I was forwarded this screenshot and it just is living rent free in my head right now.

    In conversation about 6 months ago from infosec.exchange permalink

    Attachments


    1. https://media.infosec.exchange/infosec.exchange/media_attachments/files/113/766/372/583/509/013/original/558b18b47adc8848.jpeg
  11. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Tuesday, 31-Dec-2024 13:09:48 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Graham Sutherland / Polynomial

    @gsuberland my money is on Crown Sterling

    In conversation about 6 months ago from infosec.exchange permalink
  12. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Sunday, 29-Dec-2024 11:05:05 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Rich Felker

    @dalias from HIV prevention, we know that penalizing transmission is a very bad idea.

    In conversation about 6 months ago from infosec.exchange permalink
  13. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Friday, 20-Dec-2024 15:53:28 JST Sophie Schmieg Sophie Schmieg

    The tradition is only known as "the holidays" to most, but it's important to remember what we are celebrating this time of year: the Herculean effort to fix the log4j vulnerability caused by needless use of JNDI.

    In conversation about 6 months ago from infosec.exchange permalink
  14. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Friday, 20-Dec-2024 04:26:33 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Larry Garfield
    • Paul Cantrell

    @inthehands @Crell the fun thing about ostensibly defined concepts is that you get edge cases that still very much can claim to be the thing, but which have mutually empty intersection. In this case: implementing NAND gates, wires, and delay lines using Venus fly traps is programming (it's creating a Turing complete device, after all), and writing a markdown document is programming (it's telling a computer how to do stuff, after all), but their intersection is empty (unless, of course, you use a lot of Venus fly traps and implement x86).

    I feel like the world is more fun that way, compared to excluding random things.

    In conversation about 6 months ago from infosec.exchange permalink
  15. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Monday, 16-Dec-2024 10:43:21 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • wizzwizz4
    • Jason Gorman
    • Arthur Smith

    @wizzwizz4 @apsmith @jasongorman
    This is the paper. And yeah, it's as far as I know quite a nice accomplishment, even if the press releases are very cringe.
    https://arxiv.org/abs/2408.13687

    In conversation about 6 months ago from gnusocial.jp permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: arxiv.org
      Quantum error correction below the surface code threshold
      Quantum error correction provides a path to reach practical quantum computing by combining multiple physical qubits into a logical qubit, where the logical error rate is suppressed exponentially as more qubits are added. However, this exponential suppression only occurs if the physical error rate is below a critical threshold. In this work, we present two surface code memories operating below this threshold: a distance-7 code and a distance-5 code integrated with a real-time decoder. The logical error rate of our larger quantum memory is suppressed by a factor of $Λ$ = 2.14 $\pm$ 0.02 when increasing the code distance by two, culminating in a 101-qubit distance-7 code with 0.143% $\pm$ 0.003% error per cycle of error correction. This logical memory is also beyond break-even, exceeding its best physical qubit's lifetime by a factor of 2.4 $\pm$ 0.3. We maintain below-threshold performance when decoding in real time, achieving an average decoder latency of 63 $μ$s at distance-5 up to a million cycles, with a cycle time of 1.1 $μ$s. To probe the limits of our error-correction performance, we run repetition codes up to distance-29 and find that logical performance is limited by rare correlated error events occurring approximately once every hour, or 3 $\times$ 10$^9$ cycles. Our results present device performance that, if scaled, could realize the operational requirements of large scale fault-tolerant quantum algorithms.
  16. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Thursday, 28-Nov-2024 03:57:23 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • Stéphane Bortzmeyer
    • John Shaft

    @bortzmeyer @shaft unfortunately only in English and German, though, my highschool French is a bit rusty

    In conversation about 7 months ago from gnusocial.jp permalink
  17. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Wednesday, 27-Nov-2024 08:59:05 JST Sophie Schmieg Sophie Schmieg
    in reply to
    • mekka okereke :verified:

    @mekkaokereke they somehow promoted me to senior staff engineer doing this, so I do hope it is mildly useful to the company.

    In conversation about 7 months ago from infosec.exchange permalink
  18. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Friday, 22-Nov-2024 03:46:34 JST Sophie Schmieg Sophie Schmieg

    Me: a SQL inner join is a pullback from category theory, an outer join is a pushforward.
    Colleague: SQL really is this lone survivor from a bygone era of computer science, where correctness still mattered.
    Me: I didn't know, I for one, am still waiting on the commutative algebra DLC, where both joins behave the same way.

    In conversation about 7 months ago from infosec.exchange permalink
  19. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Tuesday, 24-Sep-2024 15:39:01 JST Sophie Schmieg Sophie Schmieg

    Important sets:
    ℂ the complex numbers
    ℕ the natural numbers
    ℚ the rational numbers
    ℝ the real numbers
    𝕏 the set of fascists wannabes
    ℤ the integers

    In conversation about 9 months ago from infosec.exchange permalink
  20. Embed this notice
    Sophie Schmieg (sophieschmieg@infosec.exchange)'s status on Thursday, 12-Sep-2024 18:35:31 JST Sophie Schmieg Sophie Schmieg

    To correct the common misunderstanding:
    Eve (they/them), Alice (she/her), and Bob (he/him) are in a consensual, BDSM relationship, featuring Eve as service top, Alice as the bratty bottom, and Bob, who just likes to watch.

    Their safe word is "indistinguishability obfuscation"

    Eve only "breaks" Alice's encryption because she's super into it, not to cause harm.

    In conversation about 9 months ago from infosec.exchange permalink
  • After
  • Before

User actions

    Sophie Schmieg

    Sophie Schmieg

    Leading cryptography (ISE Crypto) at Google.Opinions my own.Content usually badly explained mathematics

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          41310
          Member since
          27 Nov 2022
          Notices
          51
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.