Re: Disabling Encryption and just using Port Forwarding? Can that be done?

zantar_at_verizon.net
Date: 05/14/04 

Date: Fri, 14 May 2004 19:33:50 GMT

Replying to myself here:

Searched long and wide and talked to a few people. Its not a practical
request. Why care about login security and then let the data go
plaintext. I guess s/key or something might be something to consider.

I can't find anyway to turn off the encryption and I dont know why
anyone (except this client) would ever want to.

Relevant Pages

  • Storage Architect Part 1: Re: [PATCH] speed up SATA (resend 3)
    ... READ has a smaller request size, while WRITE has a larger one or dynamic? ... offended or made to look bad, all I care about is the ... Areas effected are Low-level transport, Block, VM, scheduler, file ... Request Aging is a requirement for protecting the data commits on writes. ...
    (Linux-Kernel)
  • Re: Tuning index tablespaces
    ... written on the subject, and I'm fine with the the basic argument, which seems to be that because access is sequential rather than concurrent, no single process will execute faster by virtue of having the data and the index on separate disks. ... Process "A" couldn't care less about you and your next index read as it goes about servicing other requests. ... And then of course the next request is for an insert anyway so it even muddier still. ... separation - it was simply to ask whether it is possible to achieve a performance improvement in a dedicated index tablespace through ...
    (comp.databases.oracle.misc)
  • WTB: (still) Citizen parts.
    ... Back on March 22nd, "dAz", replying to my request for some setting parts for ... a Citizen wrist movement installed in a Bulove radio, ...
    (alt.horology)
  • RE: RE: Session & IP Spoofing
    ... You'd better care about the return traffic; without it you won't even be ... able to complete the TCP handshake to send the request. ... > gave me via an XSS the sessionID token. ...
    (Pen-Test)
  • Re: Strategy pattern / interface design arrangement
    ... IOWA apps receive an Iowa::Request object that encapsulates all of the details about the request to be handled. ... It simply serves as a superclass to define a common set of accessors and make some common code available to its subclasses, and to act as the factory to create the real request objects. ... This seems like it might be a reasonable pattern for your credit card processors, and it is easy to implement. ... Each of the real credit card processor classes implement the same API, so none of the rest of your code has to care at all what they are. ...
    (comp.lang.ruby)