> International, the Red Cross or something similar - but not Symantec, > If I would have too much money, I would give it Greenpeace, Amnesty > expensive extended code signing certificate for a free project. > And I dont believe, that any open source project/developer buys an > does solve the issue, one would need and "Extended validation code > According to my research *not* even a standard code signing certificate > in the file crosscompile-windows/CMakeLists.txt in the Maxima source. > set(CPACK_PACKAGE_VENDOR "Maxima Team") > the list of installed Programs ("Program & Features"). > That is already there - you see 'Maxima Team', after you installed it in Maybe we can leave a short notice on theĭownload page to get users informed about this.Īm um 17:53 schrieb Wolfgang Dautermann: I doubt whether a typical Windows user has knowledge about the I do not use Windows and wasn't aware of this. Thanks for your detailed answer and the link to security.stackexchange. The issue may probably go away, if more people are downloading and International, the Red Cross or something similar - but not Symantec, If I would have too much money, I would give it Greenpeace, Amnesty
I think it's better trying to avoidĪccording to my research *not* even a standard code signing certificateĭoes solve the issue, one would need and "Extended validation codeĪnd I dont believe, that any open source project/developer buys anĮxpensive extended code signing certificate for a free project. In the file crosscompile-windows/CMakeLists.txt in the Maxima source.
The list of installed Programs ("Program & Features"). That is already there - you see 'Maxima Team', after you installed it in > that at some point it might be possible to put some information in > I don't know the routine to create a Windows installer but I can imagine Am um 13:48 schrieb Daniel Volinski via Maxima-discuss:
0 kommentar(er)
