:prescript

:prescript

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Has anyone figured out how to get ssh port redirections working with
:prescript?  Every variation of the following that I can think of fails
with various errors around the ssh command.

 '(nnmail-spool-file
   (quote
    ((file)
     (pop :server localhost :port 1110 :prescript "ssh -x +C -f peorth.gweep.net -L 1110:peorth.gweep.net:110 sleep 30; sleep 1")
     )))
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE25xbugl+vIlSVSNkRAppQAKCoinhhNRuHHBDOFMDmpkMTgvH6oQCg473k
CsXGofzDvs+5mmCTmoSg2dc=
=3dbp
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Do not use Happy Fun Ball on concrete.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 

Re: :prescript

[empiric]

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> Hash: SHA1
> 

Sorry for posting out of topic, but what does Hash: SHA1 mean??  Thanks


> Has anyone figured out how to get ssh port redirections working with
> :prescript?  Every variation of the following that I can think of fails
> with various errors around the ssh command.
> 
>  '(nnmail-spool-file
>    (quote
>     ((file)
>      (pop :server localhost :port 1110 :prescript "ssh -x +C -f peorth.gweep.net -L 1110:peorth.gweep.net:110 sleep 30; sleep 1")
>      )))
> 
> -- 
> Rat <ratinox@peorth.gweep.net>    \ Do not use Happy Fun Ball on concrete.
> Minion of Nathan - Nathan says Hi! \ 
> PGP Key: at a key server near you!  \ 

-- 
Boat Drinks

Re: :prescript

[Lars Magne Ingebrigtsen]

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> Has anyone figured out how to get ssh port redirections working with
> :prescript?  Every variation of the following that I can think of fails
> with various errors around the ssh command.

What are the errors?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: :prescript

[John Saylor]

Hi

Forgive me for posting with Outlook Express, but my work obligates me to use
these foul tools occasionally. Also, it only makes me appreciate gnus that
much more.

-----Original Message-----
From: empiric <empiric@netscape.net>
To: ding@gnus.org <ding@gnus.org>
Date: Thursday, March 11, 1999 10:41 AM
Subject: Re: :prescript


>Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
>
>> Hash: SHA1
>>
>
>Sorry for posting out of topic, but what does Hash: SHA1 mean??  Thanks


Secure Hashing Algorithm 1
This is the revision of SHA [also called SHA0] which is an alogrithm to
produce a message hash [or digest] of a given file. Hashes are used to
ensure that a file is not tampered with since changing even one charachter
of a file will produce a different hash. Hashes are smaller than the
message, so they provide a means to check that a file was not changed.

Re: :prescript

[Shaun Lipscombe]

So shouldn't the hash be at the end of the body, like PGP signatures?

-- 
       (    )	
        ~oo~
         .. Gnu!
         / =\   \=
        -   -    -   =-=-The choice of the Linux generation-=-=
	

Re: :prescript

[Kai.Grossjohann]

Shaun Lipscombe <shaun.lipscombe@gasops.co.uk> writes:

  > So shouldn't the hash be at the end of the body, like PGP signatures?

It is, but there is a header `Hash: SHA1' near the beginning of the
body to indicate the kind of hash used.

kai
-- 
I like _\bb_\bo_\bt_\bh kinds of music.

Re: :prescript

[Katsumi Yamaoka]

>>>>> In <vaf1ziwgeis.fsf@ramses.cs.uni-dortmund.de> 
>>>>>	Kai.Grossjohann@CS.Uni-Dortmund.DE wrote:

kai> It is, but there is a header `Hash: SHA1' near the beginning of the
kai> body to indicate the kind of hash used.

By the way, hash function in elisp is available from

        ftp://ftp.jpl.org/pub/elisp/sha1.el.gz
-- 
Katsumi Yamaoka <yamaoka@jpl.org>

Re: :prescript

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Now, does anyone have any ideas about setting up ssh tunnels?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE26GYMgl+vIlSVSNkRAhSfAKC4/1sfZzC89DBaBC5bs5KDCSKppwCg2hmO
F30KwEccRN5bnFE9xuFoTzM=
=6/yP
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Do not taunt Happy Fun Ball.
Minion of Nathan - Nathan says Hi! \ 
PGP Key: at a key server near you!  \ 

Re: :prescript

[Neil Crellin]

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
> Now, does anyone have any ideas about setting up ssh tunnels?

First thing I do when plugged is log in to the corporate server, which
is also my pop guy, with a command like ssh -L1110:pop.work.com:110
work.com, type in my passphrase, and then have gnus slurp my mail from
localhost:1110. Works like a dream. Two-steps tho. I don't do
:prescript, and am not sure how the passphrase piece would work.

-- 
Neil Crellin <neilc@wallaby.cc>

Re: :prescript

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Following up to my own posts, I have narrowed it down to two bugs in
mail-source.

The first one is easy to fix.  In mail-source.el, there are a couple of
(partial) forms that look like this:

        (if (fboundp prescript)
            (funcall prescript)
and
        (if (fboundp postscript)
            (funcall postscript)

They need to be quoted:

        (if (fboundp 'prescript)
and
        (if (fboundp 'postscript)

otherwise the interpreter tests the fboundness of the string instead of the 
variable.

The second is a bit tougher for me to track down.  Colons in the program
string are converted to spaces.  That is, "1110:peorth.gweep.net:110"
becomes "1110 peorth.gweep.net 110".  Escaping with backslashes does not
appear to fix the problem (sigh).

Possibly more bugs to be found as I experiment.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE26eEpgl+vIlSVSNkRAuRdAKDfzUwtsPb6nkFZJ2RMCxt0/YqzxACgyLrZ
iu03WJo4qVqKriuL0aqwyL8=
=u/+t
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Happy Fun Ball contains a liquid core,
Minion of Nathan - Nathan says Hi! \ which, if exposed due to rupture, should
PGP Key: at a key server near you!  \ not be touched, inhaled, or looked at.

Re: :prescript

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

* Stainless Steel Rat <ratinox@peorth.gweep.net>  on Fri, 12 Mar 1999
| The second is a bit tougher for me to track down.  Colons in the program
| string are converted to spaces.  That is, "1110:peorth.gweep.net:110"
| becomes "1110 peorth.gweep.net 110".  Escaping with backslashes does not
| appear to fix the problem (sigh).

Hmmm... turns out this is not a bug, but an artifact of what ps(1) reports.
So progress is being made... it'll be nice to be able to use my own code
again :).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE26eSJgl+vIlSVSNkRAr9gAKCDNdRHDtGMVLaayk3zlT8NzwHG6wCfTO6u
gJzo0iWbuqda/rDB6dWURgY=
=/s6y
-----END PGP SIGNATURE-----

-- 
Rat <ratinox@peorth.gweep.net>    \ Happy Fun Ball may stick to certain types
Minion of Nathan - Nathan says Hi! \ of skin.
PGP Key: at a key server near you!  \ 

Re: :prescript

[Lars Magne Ingebrigtsen]

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> They need to be quoted:
> 
>         (if (fboundp 'prescript)
> and
>         (if (fboundp 'postscript)
> 
> otherwise the interpreter tests the fboundness of the string instead of the 
> variable.

No -- what we want to check is whether the contents of the variable is 
a function or not.  But we should first check whether it's a symbol,
since fboundp is kinda fragile.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen