Discussion
Loading...

#Tag

Log in
  • About
  • Code of conduct
  • Privacy
  • About Bonfire
Kevin Beaumont
Kevin Beaumont
@[email protected]  ·  activity timestamp 5 days ago

Microsoft says a Microsoft 365 Copilot bug has been causing the AI assistant to summarize confidential emails since late January, bypassing data loss prevention (DLP) policies that organizations rely on to protect sensitive information.

For some reason it hasn’t put out a security advisory - but instead buried it in a service alert which isn’t publicly visible.

https://www.bleepingcomputer.com/news/microsoft/microsoft-says-bug-causes-copilot-to-summarize-confidential-emails/

BleepingComputer

Microsoft says bug causes Copilot to summarize confidential emails

Microsoft says a Microsoft 365 Copilot bug has been causing the AI assistant to summarize confidential emails since late January, bypassing data loss prevention (DLP) policies that organizations rely on to protect sensitive information.
TheNovemberFella ✊🏳️‍🌈 🇺🇦☸️🛰️🚀
TheNovemberFella ✊🏳️‍🌈 🇺🇦☸️🛰️🚀
@[email protected] replied  ·  activity timestamp 5 days ago

@GossiTheDog #Microslop #Crap

  • Copy link
  • Flag this comment
  • Block
Charlie Stross and 2 others boosted
dazfuller :rickwhoah:
dazfuller :rickwhoah:
@[email protected]  ·  activity timestamp last week

This is truly glorious #AISlop from #Microslop in their "Introduction to Github" course.

I don't know why Tim is working in the opposite direction, but I can see that he never once "morges" his code back into develop, let alone doing it "continvoucly"

https://learn.microsoft.com/en-us/training/modules/introduction-to-github/3-components-of-github-flow

A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says
A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says
A visual representation of what should be the GitFlow process, showing how changes move from feature branches, to develop, release, and master. The diagram is a mess of arrows with some pointing in the wrong directions, and with multiple AI induced sentences such as "Bugfixes from rel, branch may be continvoucly morged back into develop", and no, that's honestly what is says

Components of the GitHub flow - Training

Learn to use the components of the GitHub flow
2
  • Copy link
  • Flag this post
  • Block

bonfire.mavnn.eu

News and community around mavnn.eu projects.

bonfire.mavnn.eu: About · Code of conduct · Privacy ·
Bonfire social · 1.0.1 no JS en
Automatic federation enabled
Log in
  • Explore
  • About
  • Public Groups
  • Code of Conduct