startx () { /usr/X11R6/bin/startx -- -dpi 100 ${1+"$@"} 2>&1 | tee $HOME/.X.er
r ; }
or modify .xinitrc in ~, or... What's The Right Thing(tm) to do?
[Thomas] No alias. See above.
____________________________________________________
TFTP problem
mishradk ([66]mishradk from vsnl.net)
Answered By Breen Mullins, Ben Okopnik
Hi,
I am a starter in GNU/Linux. I am using Linux Kernel 2.4.20-8 Redhat Linux
9.
I have written a TFTP client and server. I have created a UDP socket and as
per the RFC i am sending a structure with the proper TFTP header and then
data.
it is working fine and i am able to send and get files.
my problem is when i use ethereal and tell to capture the TFTP and specified
port it shows that the packets are UDP + data. I think i should get UDP
header , then TFTP header and then data. But this is not happening in my
case. My TFTP header is also coming as data.
How can I solve this problem...
[Breen] You're not by chance using a non-standard port for your tftp
server, are you? If the traffic isn't on port 69/udp, ethereal won't know
to decode it as TFTP.
[Ben] I think that your best bet would be to look at a standard TFTP
conversation and compare it to yours. There may be some subtle difference
that you're missing, or perhaps a part of the RFC that you're
misinterpreting.
I dont have any guide.. hope to get a reply and from you people.
[Ben] I have not read it myself, but I understand that Richard Stevens'
"UNIX Network Programming" series is the classic reference for this kind
of work.
Hi Breen
you are right.. i had used a non std port. so it was not showing it as TFTP.
[Breen] Hi Deepak --
I've got two requests:
1) Please don't post html. Email is a text medium.
2) When you ask a question on a mailing list, you should follow up on the
mailing list. That allows all subscribers to benefit from the answer you
receive. I've added The Answer Gang back to the recipients of this email.
Glad we were able to help you!
____________________________________________________
HTTPS question
Mike Orr ([67]LG Contributing Editor)
Answered By Jay R. Ashworth, Brian Bilbrey, Ramon van Alteren
Is there any way to have multiple HTTPS domains on the same IP/port? The
mod_ssl FAQ says name-based virtual hosts are impossible with HTTPS [1].
I've got two sites currently on different servers. Each is distinguished by
a path prefix ("/a" and "/b"), so they aren't dependent on the domain name
and can be installed in the same virtual host. The boss wants them
consolidated on one server, and to plan for additional sites in the future.
The problem is the certificates. A certificate is domain-specific, and it
looks like you can have only one per virtual host.
So person A types https://a.example.com/a/ and it authenticates fine, but
person B types https://b.example.com/b/ and gets a "domain does not match
certificate" dialog. (I have seen this in some cases, but haven't gotten it
in my tests. But it may be because we're still using unofficial certificates
and getting the "unknown certificate authority" dialog instead.) The only
solutions seem to be using a general domain for all the sites, getting a
separate IP for each one, or running them on nonstandard ports.
[1] [68]http://www.modssl.org/docs/2.8/ssl_faq.html ("Why can't I use SSL
with name-based/non-IP-based virtual hosts?")
[Jay] Correct. You can't have more than one SSL server per IP address,
because the certs are IP based, not domain name based.
They have to be, if you think about it, because you can't spoof IP [1] the
way you can spoof DNS.
[1] unless you manage a backbone. :-)
[Brian] I think, if your example is true, then [IIRC, you'll have to do
more research] you can spend the bucks to get a wildcard cert that will
handle [a-g].example.com/blah just fine. Alternatively, get extra IP
=9= |