SyGo

Members
  • Content count

    133
  • Joined

  • Last visited

Community Reputation

0 Neutral

About SyGo

  • Rank
    Best Poster in May/June 2006
  • Birthday 10/18/79

Contact Methods

  • Website URL
    http://

Profile Information

  • Gender
    Male
  • Location
    Lisbon, Portugal
  1. monitor keystrokes, user name, passwords (!), path names, access times and windows title of the active application (This includes the names / addresses of visited websites for almost all available browsers !). The information is stored in a password protected encrypted text file. each thing whicd done in personal pc In all honesty I don't think a software like that would be compatible with any anti-virus software. It would immediately get it into quarantine. Also, I have no idea where in the world you are trying to implement that, but make sure there aren't legal issues in doing so. Here in europe there are limits regarding personal privacy even in the workplace. Good luck, though.
  2. did you mess with master/slave jumpers on the drives? on some controllers having two masters or two slaves on the same BUS can render all drives inoperable.
  3. well, I never installed Solaris on a Sparc based computer, but on x86 I was never prompted about a GW after DHCP settings. What are picking something other than "none" on the Name Service screen during the install? Cumps, Sy
  4. I can open them on windows with infranview with no problem, but if I try to open them with gimp the images are in black'n'white and heavily interlaced... weird indeed.
  5. they are all .PSD
  6. Hi kippy, just received email from ma mate as under " just checked the file and it is showing up as file type = file. i think i give it the wrong extension or some how it has changed as it is not being recognised but is showing a size of 6mb" i know its not enough info but any chance to resolve it ? sometimes there are clues to what the file is if you open it with a text editor. open it up and see if there's anything on the first line like jfif (that would indicate a jpg) or BM6J (that would be a web compliant bmp).
  7. that makes no sense. photoshop files should work on any photopshop regardless of the platform it's running. are you sure they aren't compressed with StuffIt? there's a windows version so you can uncompress them. h++p://www.stuffit.com/win/expander/index.html (notice on the right of the page if it's not one of those extensions you are trying to open.)
  8. exactly, we can play the game as we choose. buy we can't ignore the legacy of C in the current scenario of programming languages. if you learn VB all you got is VB, there are no variants of VB. VB is just VB.
  9. Solaris. (favorite sound track too. )
  10. I'd go for C. knowing C will help up adapt quicker to other languages (perl, PHP, Ruby...) @screeeeeem: using phrases like "it's now old" in IT is a sure way to go insane. and catching trends will not make you a trendsetter (and that's where the money's at).
  11. hxxp://en.wikipedia.org/wiki/Comparison_of_SSH_clients choose your weapon.
  12. check out the material for the security+ certification. cheers.
  13. I don't deal with routers, but it's a pretty standard telnet connection so: http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Putty all the way.
  14. there is no "valid" authentication. you can connect to a workstation by it's hostname or ip address, but that is hardly considered authentication. that's just identification. if there's no password/digital certificate or some sort of way to guarantee the workstation you are connecting to is the workstation it clames to be, since its easy to copy a name, ip address or spoof a mac address. That's the "non-repudiation" part of the authentication, non existent in a workgroup scenario. not necessarly. some services require that you "authorize" them on the domain controler (DNS or DHCP are prime examples) but on other servers/services it's not imperative (file servers, print servers) you can still connect to these servers but you'll lose the SSO feature of a domain service. depends. is it a web-based ERP? it can have domain wide authentication (preserving the SSO) or not. if not users have to authenticate to whatever system the ERP's got going. (the ERP's own user database, some radius server gimmick, etc.) in a windows scenario IIS has the "integrated windows authentication" that can use your domain credentials to provide access, "Basic Authentication" forces you to create local accounts on the web server and users log on using those local accounts, Anonymous access is self-explanatory. in Unix you can wither set this on on the web server's config files (analog to "Basic Authentication") or via the ldap directory services (analog the "integrated windows authentication"), anonymous authentication is of course also available. that depends a lot of your ERP application. machine based authentication seems a bit shady to me, I really can't see why anyone would want to do that, it's not safe (since a person with bad intentions could be using a licit computer and thus have valid authentication credentials). if it's combined with another kind of authentication fine...by it's own...not my cup of tea. The ERP could use it's own user database (much like this forum) or use directory/domain authentication. oh, IP addresses and mac addresses are not "valid" ways to authenticate anything. IP's are dead-on easy to change, as are mac addresses easy to spoof. that sort of data is yet another layer of "non-repudiation" by itself it's useless, but combined with system logs and other paraphernalia it can solidify a case of system abuse. sure. the first set of credentials was lost when the connection was broken for "x" period of time. Unless you go through that process all over again (and yes, you can associate those two processes with this) you are, to all extents, a rogue user to the network. Truly my pleasure.
  15. oh yes, Unix sysadmins have been doing that for decades. Servers are main repositories for resources, but workstations can do that as well, it's no big deal, remeber that the distinction between server and workstation besides the OS is mostly processor/memory/storage specs, today's workstations are yesterday's servers. (microsoft implies a limit of concurrent connections for workstation operative systems, but that's not the issue here). as to security one could implement a "certain degree" of security by subnetting a network and configuring the routers and gateways accordingly. as to authentication I'm afraid that a centrelized repository would be necessary, unless you could hack a system where digital certificates would be issued and accepted by each workstation in order to guaratee it's own authentication. not necessarly. imagine the server requires's digital certificates to beeing logged on to? until the workstations athenticated with a valid certificate they would no be able to establish a valid connection to the the server. If it's advisable? well...think of the internet. a gazillion computers connected by routers and hubs, all accessing a multitude of servers all over the world. advisable? maybe not. manageble? clearly not. but it's in production right now, and it's working wonders for our economy. for authentication, logging, centrelized control over resources and clients. inabillity to control rogue servers on your network, having no directory services means you have no valid authenthicated methods, leaving you with little info about network devices on your network (IP and MAC Address) so there's no room to mitigate issues regarding hacking attacks from a given workstation. again: think of the internet: those are your problems. Domain services work in the same way as any directory service (unix ldap, novel, etc). it authenticates workstations, users or both. it centrelizes access to resources, not only other services on the server but on other servers, and even other network devices (like printers). A directory server will also deliver logs useful to keep your network up and running. why? if you are in a workgroup enviornment you are not authenticated to anything. when you are connected to the internet you are not authenticated to anything. (dsl, ppp connection are "somewhat" authenticated, but that's not the issue here. ) but I'll play along: in windows systems in a domain scennario you have to options to logon: local or domain. if you logon to domain you are authenticated for that specific domain. if you logon locally you are logged on to the computer. (if you want to call that "local SAM", fine I can live with that) but mind this: if you authenticate to the domain and you loose the network connection you are NOT by default authenticated locally, actually you can never be logged on to the local machine one you connect to the domain in the first place.