Event JSON
{
"id": "5ba19c7649f7c4b2443562b7df2d61caec5e8de8561133bcb57c2316c713884c",
"pubkey": "9863f8a4e2fc0f43aa3a093f5ab98f0d6cba3a25ad893817a53677e32405416b",
"created_at": 1762786400,
"kind": 1,
"tags": [
[
"t",
"copilot"
],
[
"t",
"github"
],
[
"t",
"copilotcli"
],
[
"t",
"ia"
],
[
"t",
"security"
],
[
"proxy",
"https://mamot.fr/users/yoannsculo/statuses/115525969541897078",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub/"
]
],
"content": "J'étudie GitHub Copilot CLI et ça me donne des sueurs froides sur les problématiques de sécurité 😱 😱 Les tutos de **GitHub** incitent à utiliser « --allow-all-tools » \"To reduce repetitive effort with shortcuts that boost speed and efficiency.\" On laisse donc l'IA lancer des commandes dans son terminal, avec les droits de l'utilisateur, sans aucune validation humaine. What could go wrong? 🤯 \n\nhttps://github.blog/ai-and-ml/github-copilot-cli-101-how-to-use-github-copilot-from-the-command-line/\n\n#copilot #github #copilotcli #ia #security",
"sig": "cbdbd6be0c8f61bbf18cc65dd2af14ac3a6e118e8dc6c88cf1d525efc0ffa39767f377e5fd5846679d2633f09c98a78f1a11ca2d15624f52358da6bbb6fbf63a"
}