Hotplugging USB sccanner in FC5, device not detected
by Richard England
I tried this in the previous thread but perhaps it was to buried in the
thread to be picked up on. One more time and I'll leave everyone in peace.
When I plug in my Canon LiDE 30 USB scanner into my FC5 box and fire up
Xsane, it announces that it cannot find a scanner. However, if I leave
it plugged in, logout, and log back in, then Xsane finds the scanner and
every thing works swimmingly. Under FC3 it does not seem to matter.
Hot plugging the scanner works fine.
Can anyone shed light on why the "hot plug" capability is not working
for FC5? I did notice the "hot plug" scripts are gone but I assumed
that was because UDEV (or HAL, or something else) was suppose to take
care of this.
Any assistance or enlightenment would be appreciated. Is there a good
tutorial on UDEV etc. that might tell me what is suppose to take place
so I can attempt a debug?
Thank you,
--
--R
------------------------------------------------------------------------
/Linux, and Open Software, an alternative./
Registered Unix <http://counter.li.org> user #409453
18 years
How to start applications at login in FC5?
by WipeOut
Hi,
I have just upgraded from FC3 to FC5.. I really love the new version..
Just having one issue right now..
In FC3 if I had GAIM open when I logged out it would open when I logged
in automatically.. With FC5 id doesn't, I have to open it manually each
time..
How do I manage applications that startup when I login in FC5?
Thanks
18 years
RE: On passwords, securtiy and real -sweat, blook and tears- life
by Kwan Lowe
> A common problem with passwords are their guessabilty (yes, as a
> non-native English speaker, I too make up words.....). For instance,
> even though I have taught my daughter to not use dictionary words, names
> etc, her password for one of the online accounts got hijacked. What
> happened was, she used: _____ (five underscores) as a password: arghghgh.
I'm not convinced that it's the guessability of passwords that's their downfall.
>From what I've seen, the biggest problem is clear-text passwords moving naked across
the Internet. For example, many of us are subscribed to various lists. Many of them
send a password reminder once a month in plaintext. Many people use the same
passwords across multiple sites. This means that anyone who has access to the mail
(the ISP, an administrator, etc.) has access to possible multiple passwords. Then
there are un-encrypted web logins. You can easily see in firewall rules, proxys and
just by sniffing either side of the connection what the passwords are.
Which leads to how supposedly "encrypted" passwords are stored and sent...
When a password is sent, it's rarely sent as plaintext anymore. This doesn't mean
it's. In some cases the password is "hashed" locally and the hash, rather than the
password is sent. On the other side, the hash is compared with a stored hash and
verified if they are the same. On the most rudimentary systems you could replay the
hash send and gain access. On other systems, the remote site will send some sort of
salt value that changes on each connection. So you'd think that if you get the hash
there's no way to get the password? Alas no.. It's possible to create a dictionary
of pre-hashes. I.e.,, take all permutations of allowed password characters and then
create a table listing the hash and the plaintext. When you receive a hash, just do
a lookup and you'll often locate the plaintext. This is made easier because people
tend to use very few of the allowed characters in a password. I.e., just letters,
numbers, and the occasional punctuation mark.
So your daughter's password could have been compromised by the fact that it was a
simple password and very easy to "shoulder surf", it's in a pre-hashed dictionary,
it was transmitted in the clear, it was replayed... etc etc..
> But it did make me think again about the security of my home network.
> Unfortunately most passwords are dictionary words, that are easy to
> guess using f.i. the john password guesser program, combined with
> numbers and if you are lucky a special charactor or two.
>
> What I wonder about is the following:
>
> * given that all ports are closed to external contact through a physical
> allbeit consumer oriented firewall, just means I am safe for
> port-scanners. But does it mean that I am safe from cracker systems /
> programs? Is there a way to break in, without allowing external contact
> through one of the ports? (not including trojans and the like).
Not at all... Once someone gets a privileged account to run an application, it
doesn't matter what perimeter defenses are in place. Or if your Windows system is
not patched, I could conceivably send you a picture that, when viewed, launched
another application. A website could auto-install a keylogger on your browser. These
are not really troajans... In some cases I've seen very secure firewalls protecting
very insecure wireless networks. The front door is locked but the walls are
missing...
> * A second issue is: suppose I would force my family to use really
> random passwords (like characters picked from a one-time pad). And now
> suppose I lose my root-password: would I be able to rectify this,
> without destroying the data?
The root password is easily changed on bootup either by booting into single user
mode, editing with a rescue disk, etc..
>
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
18 years
fc3, fc4, fc5, grub
by Chuck Sterling
A month ago I tried to replace (not upgrade) fc3 with fc5 on my 1.7Ghz
P4 PC. It used grub to boot fc3 or WinXP Pro, and worked fine with fc3.
When I installed (not upgrade) fc5 I had it install grub. After, the
system would get to the point where it displayed "GRUB" and stopped. Not
a prompt; the system was locked up and would not answer the keyboard.
The next thing that it normally would have done, IIRC, is display
"Loading Stage Two" or something to that effect, then the boot screens.
I did not troubleshoot it or try to fix it at that time, I just
reinstalled WinXP since it was about time anyway, and did without Linux.
Later, I wound up with an older PC, a 350Mhz PII, back from my daughter,
and I reloaded WinXP Home Edition to clear the thing out and start over.
It had one 20GB IDE drive and I installed another one to load Linux. I
installed fc5 on the second drive and wound up in the same place as on
the other PC. Reinstalled WinXP (later found out that was not
necessary). Tried installing fc4; same problem. But I had read some
messages here and made notes on grub.conf. Then I got it running by
installing fc3 and its grub boot loader; the WinXP was undamaged and
both would boot and run. I had done a minimal fc3 installation to save
time, and then did an upgrade to fc4. Still boots okay. A few minutes
ago I reinstalled fc3 with all the packages. Still boots okay. Tomorrow
I may upgrade to fc4 again and see if it boots. If it does I will
probably do yet another upgrade to fc5 and see what happens.
Ramble, ramble...
Anyway, I looked over quite a few messages here and did not find any
that talk about stopping between stage one and two, unless that's what
folks are talking about when grub finds a bad grub.conf or does not find
one at all. I compared the grub.conf that was installed with the broken
fc4 and the working fc3 and they both look the same to me. Something
else I guess. I don't get it...
Is this a common problem that has already been solved? If so, someone
please point me in the right direction and help me to get the system
running and understand what is going wrong. Until this happened to my
second PC I thought it was just a machine problem; now I'm thinking
software and I'm probably not the only one.
Best regards,
Chuck Sterling
18 years
Best yum repositories for FC5?
by WipeOut
Hi,
Sorry if this has come up often, I tried searching but couldn't find the
answer..
Livna seems to have the most available packages for FC5..
RPMforge don't seem to have support for FC5 yet..
FreshRPMS have a few packages but not really that many as far as I can see..
What are all of you using?
Thanks
18 years
how to change the existing password settings on FC3
by Ankush Grover
hey friends,
I am using Fedora Core 3 as my production server for various services like
Web Services, Mail Services, FTP,CVS, Database etc. Now my server is going
live means my company's server will be accessible through Internet. Well
this server will be protected by the Cisco Pix Firewall, but as this server
will be accessible through internet few services like Mail Services, Web
Server, FTP etc will be available to our partners and to the company's
employees.
I want to increase the password security of the server like minimum 10
characters password which must contain atleast 1 alphanumeric character and
atleast 1 Upper Case letter. Moreover if somebody tires to put his or
her last or middile or first name that should not be accepted.
for example if a user with name john abrahim is there while entering the
password if the user gives john or abrahim in his password it should be
rejected, I have seen some of the sites do like this(hotmail).
I can change the minimum password length from 5 to 10 characters or may be
to 8 characters by editing the file /etc/login.defs but this setting will
only work for the new users not for the existing users. How do I change the
password settings for the existing users and how to enforce the minimum 1
aplhanumeric & 1 upper case character in the password and the password
should not contain the first or middle or last name of the user ?
Thanks & Regards
Ankush Grover
18 years
Re: How to verify speed of a 1Gb/s network?
by Rob
gb spam wrote:
> On 4/25/06, Tim <ignored_mailbox(a)yahoo.com.au>
> wrote:
>
>>For a brute force check, you could transfer a
> large number of bytes from a byte generator
> (/dev/zero?) to /dev/nul, and time it.
>
> To transfer 1G
>
> One one host run
>
> nc -l -p 30000 > /dev/null
>
> On the other host run
>
> time dd if=/dev/zero bs=1M count=1024 | nc \
> first-hostname 30000
>
> Depending on your version of dd it may or may not
> display a throughput, so you may have to calculate
> it yourself freom the time displayed
Am I right, that the throughput here is 1 Giga BYTES,
which is 8 Giga bits?
On a 1 Gigabit/s network, this then should ideally
take about 8 seconds; right?
I do following:
master$ nc -l -p 30000 > /dev/null
slave$ /usr/bin/time -p dd if=/dev/zero bs=1M \
count=1024 | nc master 30000
which typically prints out:
real 16.20
user 0.00
sys 0.54
This means that I have effectively a network speed
of about 0.5 Gigabits/sec (as it takes 16 seconds
instead of the ideal 8 seconds).
Is my conclusion right?
Thanks,
Rob.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
18 years
opera browser
by Lonnie Freeman
I am still running FC3 with all the updates current.
I cannot get Opera browser to run! It seems to load OK, all dependancies check out, it almost starts and then crashes.
>From the command line I get a message, "cannot open x server". From the GUI I don't even get an error message.
Any ideas?
18 years
Network Manager drops wireless connections
by Chris Jones
Hi,
I've been using networkmanager for a while now, and in general have found it
to work well. However, recently it seems to have developed a problem. When
running a wireless connection it drops the connection every now and then. I
can sometimes reconnect by just clicking on the desired network again, but
sometimes I have to restart NetworkManager itself.
System :-
FC4, fully updated
kernel 2.6.14-1.1656_FC4
wireless is ipw2100
The contents of messages, related to NetworkManager are pasted below.
Does anyone else get this ? Could it be related to the firmware I am using,
which was updated a short time ago ? - I am using the freshrpms package
ipw2100-firmware (1.3-2). Could it instead be related to my wireless router ?
As an aside, how can I tell what version of the ipw2100 module comes with my
kernel ?
thanks in advance
Chris
Jan 16 18:05:13 localhost dhcdbd: Started up.
Jan 16 18:05:14 localhost dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason
Jan 16 18:05:18 localhost dhclient: Internet Systems Consortium DHCP Client
V3.0.2-RedHat
Jan 16 18:05:18 localhost dhclient: Copyright 2004 Internet Systems
Consortium.
Jan 16 18:05:18 localhost dhclient: All rights reserved.
Jan 16 18:05:18 localhost dhclient: For info, please visit
http://www.isc.org/products/DHCP
Jan 16 18:05:18 localhost dhclient:
Jan 16 18:05:18 localhost dhclient: Listening on LPF/eth1/00:04:23:8b:7c:60
Jan 16 18:05:18 localhost dhclient: Sending on LPF/eth1/00:04:23:8b:7c:60
Jan 16 18:05:18 localhost dhclient: Sending on Socket/fallback
Jan 16 18:05:18 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255
port 67
Jan 16 18:05:19 localhost dhclient: DHCPNAK from 192.168.1.1
Jan 16 18:05:19 localhost dhclient: DHCPDISCOVER on eth1 to 255.255.255.255
port 67 interval 8
Jan 16 18:05:20 localhost dhclient: DHCPOFFER from 192.168.1.1
Jan 16 18:05:20 localhost dhclient: DHCPREQUEST on eth1 to 255.255.255.255
port 67
Jan 16 18:05:20 localhost dhclient: DHCPACK from 192.168.1.1
Jan 16 18:05:20 localhost dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name
Jan 16 18:05:20 localhost NetworkManager: <WARNING> (): get_ip4_string():
error calling 'domain_name', DHCP daemon returned error
'org.freedesktop.DBus.Error.UnknownMethod', message 'Method "domain_name"
with signature "" on interface "com.redhat.dhcp.dbus.get" doesn't exist '.
Jan 16 18:05:20 localhost dhclient: bound to 192.168.1.100 -- renewal in 76403
seconds.
Jan 16 18:05:48 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:05:48 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:06:09 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:06:09 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:08:09 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:08:09 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:12:09 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:12:09 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:14:10 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:14:10 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:18:10 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:18:10 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:20:11 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:20:11 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:24:11 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:24:11 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:26:12 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:26:12 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:28:12 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:28:12 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:30:12 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:30:12 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:32:12 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:32:12 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:34:13 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:34:13 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:36:13 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:36:13 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:38:13 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:38:13 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:40:14 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:40:14 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:44:14 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:44:14 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:46:15 localhost NetworkManager: process_scan_results: assertion
`res_buf_len > 0' failed
Jan 16 18:46:15 localhost NetworkManager: <WARNING> ():
nm_device_wireless_process_scan_results(eth1): process_scan_results()
returned an error.
Jan 16 18:48:45 localhost dhclient: Internet Systems Consortium DHCP Client
V3.0.2-RedHat
Jan 16 18:48:45 localhost dhclient: Copyright 2004 Internet Systems
Consortium.
Jan 16 18:48:45 localhost dhclient: All rights reserved.
Jan 16 18:48:45 localhost dhclient: For info, please visit
http://www.isc.org/products/DHCP
Jan 16 18:48:45 localhost dhclient:
Jan 16 18:48:45 localhost dhclient: Listening on LPF/eth1/00:04:23:8b:7c:60
Jan 16 18:48:45 localhost dhclient: Sending on LPF/eth1/00:04:23:8b:7c:60
Jan 16 18:48:45 localhost dhclient: Sending on Socket/fallback
Jan 16 18:48:45 localhost dhclient: DHCPRELEASE on eth1 to 192.168.1.1 port 67
Jan 16 18:48:46 localhost NetworkManager: compute_nameservers: assertion
`config != NULL' failed
18 years
Learning procmail
by Paul Michael Reilly
I have begun the process of learning how to use procmail to filter
incoming mail messages. I see that Fedora embeds procmail into the
sendmail configuration files. What I would like to do is either find
some kind of tutorial or some mechanism that I can use to bootstrap my
knowledge by doing something and seeing some result, most likely in a
log file (and eventually in a mail buffer). Any suggestions?
Thanks
-pmr
18 years
