anzio 15.2...need a tip

[Bob Rasmussen]

On Mon, 6 Dec 2010, Fairlight wrote:

> I'm wondering if it finally -doesn't- require a password to be stored in
> 16.x.  It does in 15.x, even if you supply an ssh key.  That's the whole
> point of the key is to authenticate...  If an ssh key is provided, the only
> time I should be prompted for a passphrase is if my ssh key has a
> passphrase, which it does not.  But it's specifically asking for my
> passWORD, which is just silly if it has the key.
> 
> Was this addressed in 16.x, by any chance?

It's an option in 16, and may have been in 15. If you're using a 
public/private key pair, the private key (the piece on the PC) may or may 
not require a password/passphrase. If it does, then Anzio will ask you, 
and v.v., except as follows.

Note that you might not know what authentication mechanism Anzio was 
using. That is, it might have tried and failed with a key pair, and be 
trying with keyboard-interactive (available in 16) or host password 
authentication. The only way you'll know for sure is to check Debug 
Communication (in the Diagnose menu)

If Anzio has a stored password, and Login Wizard is turned on, and either 
the host or the private key requires a password, Anzio will supply it 
automatically ONLY IF you go to Edit:Advanced options:Security, and enable 
"Allow saved password in SSH". This has some obvious security 
ramifications.

I'm trying to work out Kerperos single-sign-on, but it's a bear.
 
> That would work, but I wouldn't even say it needs to be recoded that far.
> I mean, ideally, yeah...  But I'd settle for simply keeping window position
> from origin anchored, and shrink the window by one display line's
> worth when both status and gauge are turned off, and grow it again when the
> bar needs displaying or if the status or gauge are turned on.  The last
> time I can remember a physical terminal having a display line below the
> usable terminal area was a z49 in 1992.  And if memory serves, that space
> was reclaimable if you disabled it.

Wyse and VT terminals have a status line either above or below, I don't 
remember. It's not necessarily obvious, because there is no surrounding 
border.
 
> Either would work for me, but kill the evil blank line.  :)  I think I'd
> seriously update if that one thing was done.  *laugh*
> 
> > The status venue is still there, but the terminal looks cleaner to us.
> > 
> > It matters.
> 
> Yeah, gotta concur.  Actually, a system clock in the status bar might
> be nice.  That's the only reason I used to keep it on in a z29/z49
> configuration.  That, and there was a sysinfo program on BSD that would
> let you utilise that hardware status line to display not only the time,
> but the system load average.  It might be nice if it was something that
> could be controlled by escape codes, and not hardwired...  Implement -both-
> Brian's suggestion of moving the existing status bar to a window decoration
> status area (which could be disabled, like most other programs allow),
> and my suggestion about grow/shrink for gauge, but also have a hardware
> status bar that doesn't have the Anzio version and stuff in it, but which
> is essentially extra programmable stateful information like the old sysinfo
> setup I used to love.  Best of all worlds, there.

Windows has a perfectly good time-of-day clock. Or do you mean you want 
the HOST system's time?

> The reality is that you likely don't get complaints from garden variety
> users.  Hardcore UI freaks that have designed UI after UI over the years
> will pick at something for hours that "just doesn't feel right".  I can't
> tell you the number of hours I've spent in pTk adjustin widgets "just so"
> to get rid of a 2px imbalance between two side-by-side frames that -should-
> have been 100% equal, but were not.  And yes, I can tell a 2px difference.
> Sad, but true.  As my ISP's general manager knows all too well, I'm not
> your garden variety user.  :)

The problem from my standpoint is that frequently what's an important 
look-and-feel issue to one person is completely different from that for 
another person.

> 
> And actually, now that I have NitroPDF, passthrough printing may actually
> be something I'd use.  That's the default print driver on my system.  So I
> could print straight to PDF on Windows from Unix within my session...which
> is...well, cool.  

No need for Nitro. AnzioWin can produce PDFs itself, including from PCL 
data, including with overlays.

> 
> I'm not sure I would fully drop PuTTY yet.  With a couple tweaks, I might
> consider it, though--especially if SCP were added.

Version 16.2 - try it, you'll like it.

Regards,
....Bob Rasmussen,   President,   Rasmussen Software, Inc.

personal e-mail: ras at anzio.com
 company e-mail: rsi at anzio.com
          voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
            fax: (US) 503-624-0760
            web: http://www.anzio.com
 street address: Rasmussen Software, Inc.
                 10240 SW Nimbus, Suite L9
                 Portland, OR  97223  USA