Should a knife maker be held liable and required to 'fix' their knives when their knives are used in criminal acts? If the knives are made specifically with the sole purpose of breaking the laws, then yes, the knife maker should be held liable. If the knives are general purpose tools, then no, the knife maker has nothing to do with it. You can even kill someone with something as innocent as pillows. There is no end to human ingenuity, including their ability to commit crimes.
This is the case of security vendors trying to shift responsibility and blame to the language makers. Technology keeps changing and those AV folks need to keep up. On Wednesday, August 24, 2022 at 4:37:54 AM UTC+7 harald....@gmx.net wrote: > UPX, the Ultimate Packer for eXecutables https://github.com/upx/upx is > also a specialized loader. Does not only shrink Go binaries, but > https://words.filippo.io/shrink-your-go-binaries-with-this-one-weird-trick/ > made me aware of it when I had fun with a discussion about container image > sizes. UPX looks like a nice horror story to feed to your InfoSec, driving > them step by step over the edge if they're so inclined. > > On Tuesday, August 23, 2022 at 11:23:48 PM UTC+2 ren...@ix.netcom.com > wrote: > >> Doesn’t a different structure as per the Go FAQ imply a specialized >> loader /runtime linker? I just assumed it did. >> >> > On Aug 23, 2022, at 1:47 PM, Ian Lance Taylor <ia...@golang.org> >> wrote: >> > >> > On Tue, Aug 23, 2022 at 9:29 AM Robert Engels <ren...@ix.netcom.com> >> wrote: >> >> >> >> I did not read the analysis - just the thread here and earlier threads >> on this subject. My understanding that even though Go is statically linked >> the loader does relocations that confuse virus scanners. >> > >> > I'm not sure precisely what you mean, but I don't think that's >> > accurate. There is no Go loader. The statically linked binary >> > produced for a pure Go executable has no run-time relocations at all. >> > >> > My assumption--and it is just an assumption--is roughly the reverse: >> > because pure Go programs are statically linked, and because the symbol >> > table does not use the same names as a default C symbol table, a virus >> > scanner has a harder time seeing which system calls are being used. >> > Of course the same would be true for a statically linked C program, >> > but perhaps malware writers tend to steer clear of those. >> > >> > Obviously anything that Go is doing can also be done in C, but the >> > malware authors do have to work a bit harder to do that. >> > >> > Ian >> > >> > >> >> On Aug 23, 2022, at 11:05 AM, Brian Candler <b.ca...@pobox.com> >> wrote: >> >> >> >> >> >>> On Tuesday, 23 August 2022 at 16:49:57 UTC+1 ren...@ix.netcom.com >> wrote: >> >>> >> >>> I think what is being suggested that if the sec team bans all >> applications that exhibit dynamic code loading behavior they’d be safer - >> which would catch a lot of apps in the net. >> >> >> >> >> >> But the article quoted makes the opposite point: "Go binaries are >> often statically linked—meaning that all necessary libraries are included >> in the compiled binary" >> >> >> >> It also says: "Go’s large binary size causes analysis issues for some >> AV vendors since several security products struggle to handle larger files >> and have been known to just stop scanning and pass a binary if it is above >> a specific size." >> >> >> >> ROFL! >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "golang-nuts" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to golang-nuts...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/73a6a242-ce44-4a48-8794-6f67a4b78167n%40googlegroups.com. >> >> >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups "golang-nuts" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an email to golang-nuts...@googlegroups.com. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/DD066646-3624-4DF3-8634-44229425CF87%40ix.netcom.com. >> >> >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "golang-nuts" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to golang-nuts...@googlegroups.com. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/golang-nuts/CAOyqgcW4kJbMswGH18fRrX66-Ty3nGrYRDpnWQcf9H56Wrnsew%40mail.gmail.com. >> >> >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/82387306-c342-48d5-8a25-07f2eaeab424n%40googlegroups.com.
