public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Zachary Kline" <klinez@onid.orst.edu>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Slackware and IBMTTS: Progress, sort of
Date: Sun, 16 Mar 2008 12:54:48 -0700	[thread overview]
Message-ID: <000301c8879f$97987500$e0f7c180@ZKMOBILE> (raw)

Hi,
    I appear to have found a bug, or at least an incompatibility, in 
Slackware, specifically its version of losetup and related tools, which is 
causing me a great deal of problems.
    The voxin-installer.sh cannot mount the encrypted filesystem because 
Ubuntu and Debian have, apparently, different ways of dealing with the 
password.  By default it seems that Ubuntu and Debian hash the password, and 
Slackware's version of losetup doesn't know about this--is it an earlier 
version?  Anyhow, when I try mounting on it, I get an error about unknown 
filesystem type: naturally, since the password I'm given which is entirely 
correct is being given raw to the encryption engine, unhashed.
    I'm not quite sure what to do about this.  According to
http://www.linuxquestions.org/questions/linux-security-4/encrypted-filesystem-wont-mount-because-of-different-version-of-losetup-616885/
there is a -n option to the Ubuntu/Debian version of Losetup which will 
bypass the hash.  I don't have that version, however, and I don't have any 
version of Ubuntu or Debian handy at the moment.  Mildly annoying.
    Any advice from anybody here as far as that goes?  I'd really appreciate 
it.  Gils?
Thanks much,
Zack.



             reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Zachary Kline [this message]
 ` Christopher Moore
   ` Zachary Kline

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='000301c8879f$97987500$e0f7c180@ZKMOBILE' \
    --to=klinez@onid.orst.edu \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).