headers
Bill Moseley | 1 May 2005 01:29

Re: SSH Blocking (and then IMAP passwords)

On Mon, Apr 25, 2005 at 02:26:04PM -0700, Beretta wrote:
> The windows ssh client PuTTY.exe will easily fit on a floppy disk (368KB) and
> the private key half of a private/public key pair should consume around 2KB (for
> a total of 370KB) Of course, I personally prefer to keep my stuff on a USB
> thumbdrive as they seem to be much more reliable than floppies.

Scares the crap out of me using someone's Windows machine to connect
with putty.  I fear spyware key loggers.  I assume they exist.  I
used to carry a small bootable linux distribution, but I can't always
convince people to let me boot off it.

I guess you cannot trust any machine you use that isn't your own.

Single use passwords are a good idea, but seems like a pain to use.
When working from a remote machine I often connect multiple times
during the same session (yes, I also use screen).

One hole I worry about is web mail.  I setup webmail (over SSL) for my
wife to use, and disabled her account so no ssh logins.  Again, it's
that fear of someone snooping.  But, I get lazy and use the webmail
access once in a while, and although it's over an SSL connection I'm
typing my password in on an untrusted machine.

I use exim4 to deliver to procmail which then delivers to Maildir
directories.  I use IMAP to access the mail with the "authpam"
authentication module.

I need to setup Courier IMAP to use a different set of passwords -- but
still have read/write access to each user's $HOME/Maildir.
(Continue reading)

Permalink | Reply | 3 comments |
headers
a.list.address@gmail.com | 1 May 2005 01:32
Picon

Re: Segmentation fault

On 4/30/05, Ritesh Raj Sarraf <riteshsarraf <at> users.sourceforge.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> a.list.address <at> gmail.com wrote:
> 
> > Anyway, I recommend you reinstall Sarge from scratch, using the
> > netinst ISO image.  Since Sarge isn't released yet, doing an upgrade
> > may not work well.
> 
> If Sarge isn't released how will installing it from scratch help ?
> 
> And Debian is known to be upgraded from releases to releases.

Sarge has not been finalized yet.  Therefore, there is a chance that
upgrading from Woody to Sarge may not work completely yet.  Since you
did upgrade from Woody to Sarge, it might not have gone completely
smoothly.  Installing clean from the Sarge installer may fix some of
the weird, hard-to-track-down problems you are having.  If you don't
want to try it, that's up to you.  :)
Permalink | Reply | 0 comments |
headers
s. keeling | 1 May 2005 01:38
Picon
Picon

Re: Problem Setting DMA

Incoming from Tim Jackson:
> >Normally I keep a copy of .config in the file /usr/src/konfig-2.6.8 and
> 
> Being a total newbie to Linux I may be talking complete *!^%  but here goes 
> anyway.  Having just compiled a kernel myself I was wondering if this would 
> work, copy the original .config file from the /boot directory into the 
> kernel source directory and uncomment the relevent line in this file 
> manually setting the value to "=y" or "=m" as appropriate.  Re compile with 
> the new (old) config file and keep everything crossed.

It does work, for a limited value of "It".  As Josh mentions, copy the
.config from the old kernel and makeoldconfig.

However, hand editing the .config yourself could easily produce
garbage.  Saying Y|M to any single prompt has a cascade effect that
affects other things.  The machinery involved knows what to do, but
likely you don't.

Experiment and see what happens, as long as you've a backout plan.

--

-- 
Any technology distinguishable from magic is insufficiently advanced.
(*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
- -
Permalink | Reply | 2 comments |
headers
Damon Chesser | 1 May 2005 01:46

Re: Problem Setting DMA

On Saturday 30 April 2005 18:38, s. keeling wrote:
> Incoming from Tim Jackson:
> > >Normally I keep a copy of .config in the file /usr/src/konfig-2.6.8 and
> >
> > Being a total newbie to Linux I may be talking complete *!^%  but here
> > goes anyway.  Having just compiled a kernel myself I was wondering if
> > this would work, copy the original .config file from the /boot directory
> > into the kernel source directory and uncomment the relevent line in this
> > file manually setting the value to "=y" or "=m" as appropriate.  Re
> > compile with the new (old) config file and keep everything crossed.
>
> It does work, for a limited value of "It".  As Josh mentions, copy the
> .config from the old kernel and makeoldconfig.
>
> However, hand editing the .config yourself could easily produce
> garbage.  Saying Y|M to any single prompt has a cascade effect that
> affects other things.  The machinery involved knows what to do, but
> likely you don't.
>
> Experiment and see what happens, as long as you've a backout plan.
>
>
> --
> Any technology distinguishable from magic is insufficiently advanced.
> (*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.
> - -
Welcome back S!

--

-- 
Damon L. Chesser
(Continue reading)

Permalink | Reply | 0 comments |
headers
Damon Chesser | 1 May 2005 01:47

Re: Problem Setting DMA

On Saturday 30 April 2005 18:38, s. keeling wrote:
> Incoming from Tim Jackson:
> > >Normally I keep a copy of .config in the file /usr/src/konfig-2.6.8 and
> >
> > Being a total newbie to Linux I may be talking complete *!^%  but here
> > goes anyway.  Having just compiled a kernel myself I was wondering if
> > this would work, copy the original .config file from the /boot directory
> > into the kernel source directory and uncomment the relevent line in this
> > file manually setting the value to "=y" or "=m" as appropriate.  Re
> > compile with the new (old) config file and keep everything crossed.
>
> It does work, for a limited value of "It".  As Josh mentions, copy the
> .config from the old kernel and makeoldconfig.
>
> However, hand editing the .config yourself could easily produce
> garbage.  Saying Y|M to any single prompt has a cascade effect that
> affects other things.  The machinery involved knows what to do, but
> likely you don't.
>
> Experiment and see what happens, as long as you've a backout plan.
>
>
> --
> Any technology distinguishable from magic is insufficiently advanced.
> (*)    http://www.spots.ab.ca/~keeling      Please don't Cc: me.

skeeling,
ignore my last email, got confused over which list I was looking at.  Doh!
> - -
(Continue reading)

Permalink | Reply | 0 comments |
headers
Randy Belk | 1 May 2005 02:10
Picon
Favicon

this is a test

this is a test
Permalink | Reply | 0 comments |
headers
Vegard|drageV | 1 May 2005 02:24
Picon

Recommended kernel?

I wish to try a 2.6. kernel, running 2.4.27-1-386 now. Can someone
recommend a specific kernel for me (stable, few critical bugs)?

Heard about the cdrecord bug in 2.6.8 and 2.6.9, wich makes these two
not an alternative. I have never compiled a kernel, and are therefor
looking for a custom kernel.

Cheers, Vegard
Permalink | Reply | 9 comments |
headers
Randy Belk | 1 May 2005 03:07
Picon
Favicon

this is a test

this is a test
Permalink | Reply | 0 comments |
headers
hja123 | 1 May 2005 03:04
Picon
Picon

Re: Re: permission problem

Basically, i change all the dirs and files to rwx for owner, group and
others.

BTW, in the tick box for permission, what does a shaded box mean?

hja123
Permalink | Reply | 1 comment |
headers
Robert Storey | 1 May 2005 03:35

Re: localhost vanished

On Fri, 29 Apr 2005 19:07:39 +0530
Joydeep Bakshi <hizibizi <at> spymac.com> wrote:

> On Thursday 28 Apr 2005 6:43 pm, Kent West wrote:
> > Jpydeep Bakshi wrote:
> > >I have just checked  *ping 127.0.0.1* and have found  *network
> > > unreachable*
> >
> > What does "/etc/network/interfaces" look like?
> >
> > enjae[westk]:/home/westk> cat /etc/network/interfaces
> > # /etc/network/interfaces -- configuration file for ifup(8),
> > # ifdown(8)
> >
> > # The loopback interface
> > # automatically added when upgrading
> > auto lo
> > iface lo inet loopback
> 
> I have the above lines in my /etc/network/interfaces
> >
> > # The first network card - this entry was created during the Debian
> > installation/etc/network/interfaces
> > # (network, broadcast and gateway are optional)
> > # automatically added when upgrading
> > auto eth0
> > #iface eth0 inet static
> > #       address 192.168.123.2
> > #       netmask 255.255.255.0
> > #       network 192.168.123.0
(Continue reading)

Permalink | Reply | 0 comments |

Gmane