From: santosh on 27 Aug 2007 11:27 Betov wrote: > santosh <santosh.k83(a)gmail.com> �crivait news:fauj7t$oa5$1(a)aioe.org: > >> Also Betov comment on hidden files and folders in Linux is > disingenuous. >> Windows has them too. In fact, IIRC, you _cannot_ move or delete > certain >> files and folders in Windows, even as an "administrative" user. Much > more >> of a "Big Brother" attitude than Linux > > You like it or not, i *NEVER* downloaded anything under Windows, > without knowing what, how and where. And i never saw any download > of mines going magically into any hidden Folder. > > To be compared to Linux, where 9 times on 10, it is not possible > to know *what* (???!!!...), nor how, and surely never *where* it > goes. We are luky when it comes with a Menu Item (without asking, > of course), and when it works. Then, when it works we are luck if > this is something we wanted to have. If you right-click on an installed package in synaptic and select 'properties', and select the 'Installed Files' pane, you can see a list of where every file in the package was installed into your system. > I just went for a News Reader. Hope to find out something called > "News Reader", or "gnews", or whatever, that would make sense. Why not see the 'Newsgroup' item in the category side pane of synaptic? > Nope. I found out a package wich is supposed to have a News Reader > inside. I download it... Half an hour... Over. Silent. Fortunatly, > i see new items in the main menu... No news reader. 6 "things" > more on disk. How to remove them? No idea. No Un-install of course. Just find out the name of the package and search for it in synaptic. Once located, right click it and select 'Mark for Removal' or 'Mark for Complete Removal' For example let us say you see a menu item called 'foobar' and you want to remove it. Unfortunately you do not know which package it belongs to. Just open synaptic, press CTRL-F and type the name 'foobar'. synaptic will list all packages with 'foobar' occurring in their name and/or description. Also you can do, from the command line: $ dpkg-query --list *foobar* or $ dpkg-query --search *foobar* Omit the '*' wildcard for an exact match. Also, for package 'nnn' you can do: $ dpkg-query --listfiles nnn to list all the files in the package.
From: santosh on 27 Aug 2007 11:30 Betov wrote: > CodeMonk <jascwa(a)yahoo.com> �crivait news:kGAAi.36284$t9.18582 > @bignews7.bellsouth.net: > >> While I *think* I'm actually beginning to have an appreciation for >> your sense of humor > > :)) > > Too bad there was no humour, at all, in: > > "By looking at the productivity of the users". > > Fact is that embeeding the sources inside the PEs has been the > second best decision i ever took (the first one was the Right- > Click features). > How is this, if the basic design is wrong? One possible problem is that when distributing RosAsm programmes via email, many email providers may flag the binary as containing a "virus", since they automatically scan all email attachments. A zip of just the sources alone will avoid this.
From: santosh on 27 Aug 2007 11:32 CodeMonk wrote: > Betov wrote: >> >>> I don't see any sense to embed the the source within the binary. >> >> Simplicity of the management. Security. Speed of developments. >> > > I know I said I'd leave you alone, but this is twice now you've said > this method is more secure. Ok, assuming I agreed with the simplicity > and speed arguments, explain how this method implies security. > > You said the executable portion of the PE is always based on the > source embedded. So if I pop open my hex editor and modify the source > which is embedded - because I can since it is neither compressed nor > encrypted - when I launch the application, will it detect the change > and recompile before actually executing? Only if you launch it from within RosAsm. Otherwise the Windows loader knows nothing about embedded sources and their synchronisation with the rest of the binary.
From: CodeMonk on 27 Aug 2007 11:40 Betov wrote: > >> when I launch the application, will it detect the change >> and recompile before actually executing? > > Yes, it will detect it immidiatly, and warn you that the > file has been modified, and that you should suspect a Virus. > That's a relief :) - Scott
From: santosh on 27 Aug 2007 11:40
Betov wrote: > CodeMonk <jascwa(a)yahoo.com> �crivait news:BiBAi.36305$t9.10454 > @bignews7.bellsouth.net: > >> Ok, assuming I agreed with the simplicity >> and speed arguments, explain how this method implies security. > > How do you want to loose a Source that is comming with the > PE, as well as Resources and all? What more secure than this > could you imagine? Saving the whole thing several times? Yes, > this also is already implemented:[Ctrl]/[K] incremental saving. Provide an option for encrypting the sources and it will be even more "secure". >> when I launch the application, will it detect the change >> and recompile before actually executing? > > Yes, it will detect it immidiatly, and warn you that the > file has been modified, and that you should suspect a Virus. Ah, so you store a checksum for the source section and add a stub to the executable section that compares this checksum against a newly generated one? Also have you noticed any slow-down in loading time for files with large sources? Just imagine a RosAsm app which had about, say, 50 Mb of source embedded in it. Will this cause problems during loading? Any idea? |