cm0002@digipres.cafe to Opensource@programming.dev · 17 hours agoAndroid syncthing repo gone and Developer profile gone private.github.comexternal-linkmessage-square11fedilinkarrow-up171arrow-down11cross-posted to: [email protected]
arrow-up170arrow-down1external-linkAndroid syncthing repo gone and Developer profile gone private.github.comcm0002@digipres.cafe to Opensource@programming.dev · 17 hours agomessage-square11fedilinkcross-posted to: [email protected]
minus-squaresomewa@suppo.filinkfedilinkarrow-up2·2 hours agoIf he pushed something he shouldn’t have online then taking it offline immediately makes a lot of sense.
minus-squareorygin@piefed.sociallinkfedilinkEnglisharrow-up3·edit-246 minutes agoIt makes sense, but once it’s pushed there is no way to know if it’s been cloned or kept somewhere else. The only real mitigation is to rotate the keys or password that was leaked. If it’s something else you can’t rotate, you’re screwed.
minus-squareonlinepersona@programming.devlinkfedilinkarrow-up3·43 minutes agohttps://trufflesecurity.com/blog/anyone-can-access-deleted-and-private-repo-data-github
If he pushed something he shouldn’t have online then taking it offline immediately makes a lot of sense.
It makes sense, but once it’s pushed there is no way to know if it’s been cloned or kept somewhere else. The only real mitigation is to rotate the keys or password that was leaked.
If it’s something else you can’t rotate, you’re screwed.
https://trufflesecurity.com/blog/anyone-can-access-deleted-and-private-repo-data-github