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 VessOnSecurity (bontchev@infosec.exchange)

  1. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Friday, 06-Jun-2025 05:32:49 JST VessOnSecurity VessOnSecurity

    So, when are people going to start praising Musk for opposing Trump's Big Ugly Bill and Trump taking revenge on him?

    https://www.nbcnews.com/business/business-news/trump-musk-contracts-subsidies-budget-cuts-rcna211288

    In conversation about 16 days ago from infosec.exchange permalink
  2. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Wednesday, 04-Jun-2025 23:50:07 JST VessOnSecurity VessOnSecurity
    • Baldur Bjarnason
    • Lauren Weinstein

    @FediThing @lauren @baldur These wrong answers lead me to the right answer faster than a google search, for instance, so yes, it's beneficial since it saves me time. As long as you've learned not to trust is blindly - which is why I said that we should teach how to use it properly.

    In conversation about 17 days ago from infosec.exchange permalink
  3. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Wednesday, 04-Jun-2025 23:50:04 JST VessOnSecurity VessOnSecurity
    in reply to
    • Baldur Bjarnason
    • Lauren Weinstein

    @lauren @FediThing @baldur I am not talking about teaching them how AI tech works. We don't teach everybody how the internals of the computer work. I am talking about teaching them how to *use* AI properly - just like we teach kids how to use computers.

    What is the alternative? Not teach them how to use AI properly and let them try to figure it out themselves and fall for hallucinations and other bullshit?

    Oh, and you just blamed the users, BTW, by saying that they can't use security properly. Which they indeed can't - but it's our fault, not theirs, because so far we have failed to figure out how to make computer use for sensitive stuff both secure and intuitive.

    In conversation about 17 days ago from infosec.exchange permalink
  4. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Monday, 19-May-2025 17:46:30 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont

    @GossiTheDog At least they have the option to pay. Can you imagine of paying the ransom had been made illegal?

    In conversation about a month ago from infosec.exchange permalink
  5. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Monday, 05-May-2025 22:20:44 JST VessOnSecurity VessOnSecurity
    in reply to
    • Kevin Beaumont

    @GossiTheDog
    In case you missed it in the actual article:

    "The hacker was able to access data that the app captured intermittently for debugging purposes, and would not have been able to capture every single message or piece of data that passes through TeleMessage’s service."

    That is, this was only debug data, not actual logged messages. As far as I understand, the actual logs are encrypted with a password - although that probably doesn't amount to much, since the password seems to be hard-coded in the app.

    Also, you have to pick one:

    - Trump's government is bad because they use Signal's disappearing messages to avoid scrutiny

    or

    - Trump's government is bad because they complied with a judge's order to log Signal messages.

    You can't criticize them for both simultaneously and still have any credibility that your reasoning isn't obscured by your politics.

    Oh, and Telemessage was procured by the Biden administration - it is not a Trump thing. They just used it to comply with the judge's order.

    In conversation about 2 months ago from infosec.exchange permalink
  6. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Monday, 05-May-2025 02:48:03 JST VessOnSecurity VessOnSecurity

    OK, here is some additional info about the Telemessage thing found by somebody on BlueSky:

    - The hard-coded credentials are used to encrypt the collected logs.

    - They seem to be "encrypted" in a passworded archive (ZIP?). Not sure; I'm not familiar with Kotlin.

    - They are uploaded to a PostgreSQL database on a server in Israel.

    - The database is accessed by subscriber e-mail and PIN.

    - The site has been purged, which probably means that at least until the app is updated, the US government communications via Signal are no longer logged, as required by law.

    I still wouldn't call this a "backdoor" but definitely poor security practices:

    - Hard-coded credentials, duh.

    - ZIP legacy encryption is vulnerable to known-plaintext attacks.

    - Storing sensitive info on a server in a foreign country is bad - not because you can't trust the company but because you have no control of its security. What if an employee runs an info stealer and the admin password to the database gets leaked? The US government has a secure cloud, why not use that?

    Link to my conversation with the person who found this:

    https://bsky.app/profile/vure.bsky.social/post/3loe5irieck22

    In conversation about 2 months ago from infosec.exchange permalink

    Attachments


    1. https://media.infosec.exchange/infosec.exchange/media_attachments/files/114/450/651/537/795/788/original/5885e1880d23c91e.jpg
  7. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Sunday, 04-May-2025 20:38:03 JST VessOnSecurity VessOnSecurity
    in reply to
    • Kevin Beaumont

    @GossiTheDog I agree with most of your arguments. (In fact, the only one I take exception with is comparing ransomware with climate change. Ransomware is a much more real and urgent problem.) Those are pretty much arguments I've used myself when advising customers hit by ransomware not to pay.

    But, ultimately, it's the company's decision. Even if the company makes the wrong decision, the government shouldn't be the one who decides for them.

    See also this:

    https://www.coveware.com/blog/2025/4/29/the-organizational-structure-of-ransomware-threat-actor-groups-is-evolving-before-our-eyes

    "Decryption tools are worse than they’ve ever been."

    In conversation about 2 months ago from infosec.exchange permalink
  8. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Sunday, 04-May-2025 01:27:05 JST VessOnSecurity VessOnSecurity

    "Woman killed in Greece after bomb explodes in her hands":

    https://edition.cnn.com/2025/05/03/europe/woman-killed-carrying-bomb-in-greece-intl

    Infosec advice: Don't carry a bomb in your hands.

    In conversation about 2 months ago from infosec.exchange permalink
  9. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Tuesday, 29-Apr-2025 22:48:36 JST VessOnSecurity VessOnSecurity
    in reply to
    • Kevin Beaumont

    @GossiTheDog Oh, we've misunderstood each other. "Jan" is a program - a GUI for running various LLMs, not "January".

    In conversation about 2 months ago from infosec.exchange permalink
  10. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Tuesday, 29-Apr-2025 22:48:35 JST VessOnSecurity VessOnSecurity
    in reply to
    • Kevin Beaumont

    @GossiTheDog
    https://github.com/menloresearch/jan

    In conversation about 2 months ago from gnusocial.jp permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      GitHub - menloresearch/jan: Jan is an open source alternative to ChatGPT that runs 100% offline on your computer
      Jan is an open source alternative to ChatGPT that runs 100% offline on your computer - menloresearch/jan
  11. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Tuesday, 29-Apr-2025 22:46:09 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont

    @GossiTheDog Yes, that's what I tried. Said it couldn't start the server.

    In conversation about 2 months ago from gnusocial.jp permalink
  12. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Tuesday, 29-Apr-2025 20:25:17 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont

    @GossiTheDog Most of the energy is spent on training the models - not on using them.

    That said, I tried using this thing in Jan and it didn't even start. (DeepSeek runs fine.)

    In conversation about 2 months ago from infosec.exchange permalink
  13. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Tuesday, 29-Apr-2025 02:56:31 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont

    @GossiTheDog But were they Russian teenagers?

    In conversation about 2 months ago from infosec.exchange permalink
  14. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Monday, 21-Apr-2025 19:32:55 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont
    • Urwumpe

    @urwumpe @GossiTheDog As I said, I don't know enough genetics to determine by myself how unusual this is, but my dentist's sister, who is a geneticist, reached that same conclusion all by herself after looking at the genome of the virus, so it must be pretty obvious to a geneticist. It might look unrealistic and black magic to us - but then me telling somebody what a new computer virus does after just looking at a hex dump of it looked like black magic to that person, too.

    Anyway, my point is, it is fine to criticize Trump for static this as a fact, while it is only an unproven (albeit likely) theory based on some insufficient evidence. But it's definitely not correct to call it a "conspiracy theory". It's a perfectly legitimate theory, there is evidence supporting it, it's just not sufficient to prove it.

    In conversation about 2 months ago from infosec.exchange permalink
  15. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Monday, 21-Apr-2025 17:16:57 JST VessOnSecurity VessOnSecurity
    in reply to
    • Mike Masnick ✅
    • BrianKrebs
    • David Cohen

    @mmasnick @davidbcohen @briankrebs In the ruling, he seems to be saying that the White House *can* exclude journalists from the briefing - just not based on their opinions (which the government has explicitly stated was the reason)? I still don't understand how he makes the jump from "not abridging the freedom to print anything" to "not abridging their access to government briefings"...

    He seems to be basing it on some rulings "Cornelius, 473 U.S. at 806; see also Forbes, 523 U.S. at 682"; I'd have to dig up those.

    In conversation about 2 months ago from infosec.exchange permalink
  16. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Sunday, 20-Apr-2025 17:57:03 JST VessOnSecurity VessOnSecurity
    in reply to
    • Mike Masnick ✅
    • BrianKrebs

    @briankrebs @mmasnick Banning AP for refusing to comply with the "Gulf of America" name is silly, nasty, and petty - but how exactly is it an infringement on their 1st Amendment rights? Trump isn't forbidding them from printing whatever they want; he's just denying them access to a gathering in his home. (They can probably get what was said there via a FOIA, but that would be pretty useless to them, because other outlets would have already printed the information by that time.)

    In conversation about 2 months ago from infosec.exchange permalink
  17. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Sunday, 20-Apr-2025 17:57:01 JST VessOnSecurity VessOnSecurity
    in reply to
    • Mike Masnick ✅
    • BrianKrebs
    • David Cohen

    @davidbcohen @briankrebs @mmasnick But why? What was his argumentation? Clearly, there is nothing in the 1st Amendment that mentions these places or excluding journalists from them. It mentions "not abridging the freedom of the press" and "the right to peacefully assemble" - but it seems pretty obvious to me that this means not preventing the press from printing anything they want - not preventing it from assembling in the White House...

    In conversation about 2 months ago from infosec.exchange permalink
  18. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Wednesday, 16-Apr-2025 04:50:19 JST VessOnSecurity VessOnSecurity

    Make Python Great Again! Impose tariffs on its imports!

    https://pypi.org/project/tariff/

    In conversation about 2 months ago from infosec.exchange permalink
  19. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Wednesday, 16-Apr-2025 03:08:47 JST VessOnSecurity VessOnSecurity

    A report on ransomware from a cybercrime specialist at the Dutch police. Sadly, in Dutch, but Google Translate makes it reasonably understandable:

    https://www-digitaltrustcenter-nl.translate.goog/veel-bedrijven-hebben-eigenlijk-geen-keuze-tussen-betalen-of-niet-betalen?_x_tr_sl=auto&_x_tr_tl=en&_x_tr_hl=en-US&_x_tr_pto=wapp

    Some highlights:

    - Companies with a cyber insurance are asked higher ransoms. Not clear who pays it - they victims or the insurance company.

    - Trade, construction, and the ICT sector (whatever that is) are targeted most often.

    - Most companies have no option but to pay. In 5% of the cases the company could recover by other means but chose to pay nevertheless, because it was faster and cheaper. In the remaining 95% the only alternative to not paying was bankruptcy. But sure, let's make ransom payments illegal...

    In conversation about 2 months ago from infosec.exchange permalink
  20. Embed this notice
    VessOnSecurity (bontchev@infosec.exchange)'s status on Saturday, 12-Apr-2025 04:38:55 JST VessOnSecurity VessOnSecurity
    • Kevin Beaumont

    @GossiTheDog They will be, if they speak out. Krebs has worked in a bunch of infosec companies - their clearances will be suspended in a snap if they speak out.

    In conversation about 2 months ago from gnusocial.jp permalink
  • Before

User actions

    VessOnSecurity

    VessOnSecurity

    Anti-virus, malware and infosec expert, crypto amateur, privacy advocate and general annoyance.PGP keyID: 0x365697c632dd98d9

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          202699
          Member since
          20 Oct 2023
          Notices
          74
          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.