Re: PGP scripting...

From: Andrew MacKenzie (amackenz@edespot.com)
Date: 01/08/03

  • Next message: Andrew MacKenzie: "Re: PGP scripting..."
    Date: Wed, 8 Jan 2003 14:08:10 -0500
    From: Andrew MacKenzie <amackenz@edespot.com>
    To: Keith Smith <keith.smith@keiths-place.com>
    
    
    

    > > > I think that client is probably worried about regular users
    > > > that will have access to the file system, rather than a
    > > > determined external hacker.
    > >
    > > How does the encrypting improve the security of storing the
    > > files in a directory, which is only readable by selected users, then?
    > >
    > > They can only manage to read them, if they obtain that
    > > particular user's UID. But if they do it, they can probably
    > > also read /proc/N/mem, effectively bypassing the encryption.
    >
    >
    > I was assuming that the files were sitting in a shared file system
    > somewhere and were world readable. Now I realise I was going out on a
    > limb trying to guess the clients reasoning, but I couldn't think of any
    > another reasons that explained the original request.
    In my scenario, the files are not in a shared location, per se. They are
    being sent by an outside source to a sftp server, and then downloaded to an
    internal machine where the processing will be done. The production machine
    won't be multi-user per se (we'll be the only ones on it). We're also more
    interested in 'external cracker' than 'internal sabotage'. This was a
    decision made by the client as well.

    I have made it clear to my client time and time again that the security of
    that box will make a bigger difference in the long run than PGP encrypting
    the files on it ever will (they implemented this PGP everything policy
    before any other security policies).

    What I'm trying to do is determine for the future the best way to keep
    files encrypted while still being able to access them through batch jobs
    (no human interaction), and process their data (un-encrypt them only while
    using them, but not storing a temporary un-encrypted form of the file).

    It sounds like having a separate 'secure' box to handle the encryption
    seems like a good way to go. This at least centralizes ones private
    key(s), and thus administration.

    -- 
    // Andrew MacKenzie  |  http://www.edespot.com
    // An intellectual snob is someone who can listen to the William Tell
    // Overture and not think of The Lone Ranger.
    
    


    • application/pgp-signature attachment: stored


    Relevant Pages

    • TLS/SSL capabilities on Outlook 2003
      ... I'm trying to figure out what my options are when it comes to encrypting the ... SMTP traffic from a client to the server. ... More specifically I want to make sure that the authentication part is ...
      (microsoft.public.exchange.clients)
    • TLS/SSL in Outlook 2003 and Exchange 2003
      ... I'm trying to figure out what my options are when it comes to encrypting the ... SMTP traffic from a client to the server. ... More specifically I want to make sure that the authentication part is ...
      (microsoft.public.exchange.admin)
    • RE: PGP scripting...
      ... I would assume that the main reason you're encrypting the data on disk ... likely can access the key files that you said are also locally on disk. ... At a very minimum, I would explain this to your client, and if they ... Just my $0.02 Whatever you do, if you learn of a Java-based PGP ...
      (SecProg)
    • Re: HDD copy protection
      ... But the problem is that ...if the client copy my hdd ...then i will ... mounted partition. ... If your client has access to the key, encrypting the partition ...
      (comp.os.linux.misc)
    • Re: Asynchronous socket programming vs. remoting
      ... You are the first person that said I should use sockets. ... them quicker than I can load them from my harddrive using the file system. ... It scales nice too - I tried throwing 400 requests at the server in a span ... > do not need the same assembly on the client and server. ...
      (microsoft.public.dotnet.languages.csharp)