Sunday, December 30, 2007

Inbow Ultrapro Dongle Emulator

OpenBSD and readonly FileSystems v1.1

This is my experience in transforming an OpenBSD firewall in a machine
with all filesystems mounted readonly, so, in case of power failure,
at the next start, the machine is ready to serve your LAN without errors
regarding filesystem integrity, like a commercial modem or firewall.



It's possibile to use a Compact Flash drive instead of an Hard Disk!



The machine will use a memory filesystem for all the read/write activities.



Before starting to work, you need the bsd.rd file. When you are ready, reboot.



The first step is to boot with the ramdisk. So:



 boot wd0a:/bsd.rd 


When the kernel is loaded and ask you what to do, press S to run the shell.



Now you need to mount all bsd partitions of the system in /mnt. For example, in my machine I have only / and /usr. So I:



 mount /dev/wd0a /mnt
mount /dev/wd0d /mnt/usr


Now, we chroot in the real / with:



 /mnt/usr/sbin/chroot /mnt 


and export some shell variables to use correctly the system:



 export TERM=vt220
export HOME=/


Now we can start modify /etc/fstab.



 vi /etc/fstab 


The first thing to do is add the line:



 swap /mfs mfs rw,nosuid,noatime,-P=/skel,-s=XXX 0 0 


and switch all bsd partitions to readonly (ro).



For example, this is my fstab:



 
/dev/wd0a / ffs ro,softdep 1 1
swap /mfs mfs rw,nosuid,-P=/skel,-s=102400 0 0
/dev/wd0d /usr ffs ro,nodev,softdep 1 2


The -s=XXX is the number of the 512-byte blocks that the memory filesystem should contain. In my fstab (((102400 * 512)/1024)/1024) = 50 MB.



Now, we have to make the directory that will stay in RAM. I choose the /mfs directory. You can use what you like, but remember to update the fstab and change all the links!



 mkdir /mfs 


Now, we have written in fstab that the content of /skel (-P=/skel) directory must be copied in /mfs at boot. So, now, all the files will be stored in /skel. Start doing:



 mkdir /skel
mkdir /skel/dev


The first step is to move all ptyp* and ttyp* files from /dev to /skel/dev



This is needed because, when we will use ssh to access the machine remotely,
the system must change owner and permission of these files. Putting them in
the /mfs/dev directory that is in ram (and is read/write), and making a
simbolic link, will solve all problems.



 mv /dev/ptyp* /dev/ttyp* /skel/dev/ 


Now we can make the rights link, but first we make a symbolic link to the real path:



 cd /mfs
ln -s /skel/dev/ .


And then:



 
cd /dev/
for i in /mfs/dev/* ; do ln -s $i . ; done


Now we can delete the /mfs/dev link:



 rm -rf /mfs/dev 


Now that the devices are ok, we must move the /root directory:



 mv /root /skel/
cd /
ln -s /mfs/root .


The /tmp directory will be in a readonly filesystem, so we can't use it.
We have to make another tmp directory in /skel called tmp2 and make a symlink.
The name tmp2 is choosen because in /var there is another tmp directory.
We need both, so one must be called differently.



 
mv /tmp /skel/tmp2
ln -s /mfs/tmp2 /tmp


Move these dirs in /skel:



 
/var/backups
/var/cron
/var/db
/var/empty
/var/log
/var/mail
/var/msgs
/var/named
/var/run
/var/spool
/var/tmp


and make a symlink in /var for each one:



 
ln -s /mfs/backups /var
ln -s /mfs/cron /var
ln -s /mfs/db /var
ln -s /mfs/empty /var
...



Now the system is perfect and it will be ready to serve you.



One last note: if you plan to acces the system with the keyboard, please comment all lines in /etc/fbtab or you will get stupid errors every time you log. (the system try to change owner and permissions of the keyboard device but that file is on a readonly filesystem.)

Sunday, September 2, 2007

Protein Pudding Instone

Fonera+ impressions

I'm a FON beta tester and some days ago I received the new Fonera+ in test. These are my impressions.



The new Fonera+ model number is FON2201. This version has changed the old logo "Movimiento FON" with a cleaner "FON spot".





The new model is bigger than the previous Fonera as it possible to see:





FON engineers included new things on the board: an internal antenna (bottom left), another ethernet port (the black one) and a new LED.





I searched the serial console on the new Fonera+ board, and I found only 4 pins... I tried to connected my serial adapter and I get the output:



 +Ethernet eth0: MAC address XX:XX:XX:XX:XX:XX
IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
Default server: 192.168.1.254

RedBoot(tm) bootstrap and debug environment [ROMRAM]
OpenWrt certified release, version 1.1 - built 22:32:28, May 7 2007

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

Board: FON 2201
RAM: 0x80000000-0x81000000, [0x80040290-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 2.000 seconds - enter ^C to abort
RedBoot> fis load -b 0x80100000 loader
RedBoot> go 0x80100000
Failsafe loader v0.2

Looking for board config data... found at offset 0xa87f0000
Reset button GPIO: 6
Reading flash from 0xa8040000 to 0xa825b989... done.
Verifying CRC... OK - 0xa7a3c6df
Uncompressing Linux... Ok, booting the kernel.
[sighandler]: No more events to be processed, quitting.
[cleanup]: Waiting for children.
[cleanup]: All children terminated.
Unlocking rootfs ...
Could not open mtd device: rootfs
switching to jffs2
init started: BusyBox v1.4.1 (2007-06-08 12:11:45 UTC) multi-call binary
: ifconfig: SIOCSIFADDR: No such device

: ifconfig: SIOCSIFADDR: No such device

: udhcpc (v1.4.1) started

: Sending discover...

: Sending select for 192.168.0.2...

: Lease of 192.168.0.2 obtained, lease time 43200

: deleting routers

: adding router 192.168.0.1

: adding dns 192.168.0.1

: udhcpc (v1.4.1) started

: Sending discover...

: Sending select for 192.168.0.2...

: Lease of 192.168.0.2 obtained, lease time 43200

: deleting routers

: adding router 192.168.0.1

: adding dns 192.168.0.1

: runlevel -> 1

: enqueued

: killall: watch_chilli: no process killed

: ERROR: chillispot is not running

: fonsmcd successfully started

: 36524 00146.187 164591.0 61.0 242031896628819.0 72097.8 0

: 56 15 * * * /bin/thinclient cron

: 51 15 * * * ntpclient -s -h ntp-1.cso.uiuc.edu


There isn't a "Press enter to activate this console" like in the previous model.

I think FON decided to use the serial console only for getting the output from the device to avoid that people can easily manipulate the Fonera+.



The firmware revision of this Fonera+ is 1.1.0 r2. Like the new Fonera firmware version, is not possible to specify a custom DNS in the configuration.



The only way to use a local DNS, or a custom one, is modify the filtering rules of the gateway witch the Fonera+ is attached.

At home I have an OpenBSD gateway that serve also as DNS caching server.

I succedeed to use my DNS server with this filtering rule in the gateway: "all traffic that came from the Fonera+ and is directed to any machine port domain, has to be redirected to my dns server":



 rdr on $int_if proto { tcp, udp } from $fonera to any port domain -> \
($int_if) port domain


I think is still possible to use the Kolofonium hack, redirecting all dns queries from fonera to the right DNS server.... I haven't tried and I'm not interested in.



I noticed that Fonera+ still NAT all traffic. From a gateway perspective, both the private and the public traffic come from Fonera+ IP. I would have liked to see that Fonera+ bridged the private network with the network it has attached, and NAT the public one ... But I think That this function will never be Implemented in the official firmware.

That's all folks!

Wednesday, August 1, 2007

Bushnell Trophy 730132p

Linux Fax Server

post being edited ...

Lately I found myself helping a friend in creating a Linux box that would act as a server with fax modem pci internal.

The basic software configuration was: Linux CentOS + HylaFAX

I must say that the installation of HylaFAX was not so difficult. The point is rather to understand how it was managed configuration and how to configure the internal pci modem.

For some reason, the internal modem pci chosen was a model conexant Chipset. We were forced to having to purchase the driver for linux for about $ 20 to use it as a fax.

After the installation of HylaFAX was necessary to run the command "faxsetup" which was a few questions about some aspects of the server, and created all the folders and files needed. After being asked if you wanted to configure the modem.

If you answered with "yes" was leaving the automatic setting of the modem, otherwise you could get the same result by manually running the command "faxaddmodem"

Once all configurations have been created two files in "/ etc / hylafax / etc / "" config. $ name "and "FIFO. $ Name", where $ name is the name of the ES: config.modem

E 'can manually edit the config file. $ Name to change some options.

Council not to raise 'faxaddmodem "!

Without this, you should use faxgetty to automatically configure the modem. Open up / etc / inittab and add the line: t2: 23: respawn: / usr / local / sbin / faxgetty nome_device

Now the server is ready to send faxes. If you do not want to receive faxes, set in the configuration of modem RingsBeforeAnswer 0.

Wednesday, July 11, 2007

How 2 Change The Thermostst On Agolf Turbo

Ubuntu e partizione /home criptata [2.0]

Recently I came to him to encrypt the partition / Home laptop.
On it, in fact, there are many many many personal information, and the loss (or abduction) of this `friend 'might be suffering even more knowing that everyone can read my data without too much difficulty.

From all the material that I found online, I have developed a simple and efficient for my purpose.

The first thing to do is install Ubuntu in the usual way, leaving plenty of unpartitioned space on the disk.

I, for example, I created a partition `root` / dev/hda1 ext3 from 10 GiB, a swap partition `` / dev/hda3 from 1.2 GiB and I left all the free space is not ` `partitioned. The space will be used by / home encrypted `/ dev/hda2`.

After installing the system, and configured everything very nicely, I installed the package `cryptsetup`.

Later, I modified the file `/ etc / modules' adding:

 ... aes-i586 dm_mod dm_crypt ... 

and I loaded the modules to be able to properly use various tools.

I also created the partition '/ dev/hda2' giving all the free space, and formatted with a filesystem with LUKS encrypted command: $ sudo

 luksFormat-t ext3 / dev/hda2 

After typing the password (nice long) and you format the file system, I modified the file `/ etc / crypttab` so that it contained:

 ... home / dev/hda2 ninth luks ... 

Then I also changed the file `/ etc / fstab` adding the newly created partition:

 ... UUID = uuid_della_nuova_partizione / home ext3 defaults, errors = remount-ro 0 1 ... 

uuid_della_nuova_partizione `where` it is calculated as:

 vol_id $ sudo-u / dev / mapper / home 

In this way, to boot automatically prompted to enter your password to mount the encrypted device.

Now, before you reboot, it is good to temporarily mount the encrypted device on / mnt and copy all the current content of the folder / home.

addition, you can also encrypt the swap partition the same way.

Add to your `/ etc / crypttab is the content:

 ... swap / dev/hda3 / dev / random swap ... 

and add (or edit the entry) to `/ etc / fstab is the value (without UUID):

 ... / Dev / mapper / swap none swap sw 0 0 ... 

Finally, unmount the swap-a swapoff and destroy its contents with: $ sudo

 dd if = / dev / urandom of = / dev/hda3 count = 100 

Now, reboot the machine and you enjoy the home and swap partitions encrypted!

Sunday, July 8, 2007

Cervix Position Right Before Period

Infostrada e blocco della connesione

E 'for some' time now that I switched on ADSL2 + network Infostrada.

I must say that overall performance has improved a lot ...

The download speeds and 'almost always about 500KiB / s (ftp, http, etc. ..), while the upload on 40KiB / s. In practice speeds are similar to when I was on the Telecom network. Now, however, also increased the overall speed of p2p that touches the 500KiB / s!

What has changed a lot, more than la velocità dal p2p, e' la latenza che è molto molto molto bassa, grazie alla configurazione ADSL2+ FAST.



Ora, quando gioco sui server di Urban Terror ho ping che variano dai 30ms ai 50ms! (In confronto ai 100ms - 120ms che avevo su rete Telecom)



Da test effettuati nessuna porta viene filtrata, diversamente da quanto accadeva su rete Telecom. Addirittura anche la porta 25 è aperta ed, in teoria, potrei mettere il mio server di posta elettronica personale... (questo però violerebbe il contratto)



Ora, in modo continuativo, dopo diversi secondi, ricevo in ingresso dei pacchetti "strani". Ecco un esempio:



 
Jul 08 11:25:47.268756 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:26:17.100807 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:26:23.953824 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.1: igmp query [tos 0xc0] [ttl 1]
Jul 08 11:26:32.045988 rule 22/(match) block in on pppoe0: 172.21.233.27.11097 > X.X.X.X.60481: R 1203762461:1203762461(0) win 0 (DF)
Jul 08 11:26:32.048143 rule 22/(match) block in on pppoe0: 172.21.161.11.11147 > X.X.X.X.61201: R 1175607756:1175607756(0) win 0 (DF)
Jul 08 11:26:32.066924 rule 22/(match) block in on pppoe0: 172.21.103.14.11191 > X.X.X.X.59672: R 1301080473:1301080473(0) win 0 (DF)
Jul 08 11:26:46.657395 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:27:16.505355 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:27:23.953778 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.1: igmp query [tos 0xc0] [ttl 1]
Jul 08 11:27:38.649488 rule 0/(match) block in on pppoe0: 151.20.91.23.3446 > X.X.X.X.135: S 3793218695:3793218695(0) win 53760 (DF)
Jul 08 11:27:46.097376 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:28:15.713670 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:28:23.954003 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.1: igmp query [tos 0xc0] [ttl 1]
Jul 08 11:28:44.957907 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:29:14.646055 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.13: ip-proto-103 34 [tos 0xc0] [ttl 1]
Jul 08 11:29:23.954456 rule 0/(match) block in on pppoe0: 151.23.227.142 > 224.0.0.1: igmp query [tos 0xc0] [ttl 1] In practice

receive packets IGMP multicast packets destined to ports 135, 445, and other port-related Microsoft protocol.

Also, when I get to run the PPPoE connection:

 pppoe0: received unexpected PADO 

But not 'always gold that glitters ... I discovered a nasty problem very annoying ...

In practice, if I leave the router connected to the Internet for "some time" without generating traffic, Infostrada me "is blocking the connection."

The "long time" is a variable size. Sometimes me and 'happened after 40 minutes of inactivity, sometimes after 2 hours of inactivity.

"I'm blocking the connection" means that the connection is actually active, the router and 'connected to the network with the IP address acquired before and can successfully ping the default gateway and still receive the "schefezze" in above. Any request

dns working properly (even those that are not in cache), but traffic and everything else '"stuck."

The only way to return to "navigate properly" is to break down the connection and restart it.

I called support several times, but tests on the line told me that the line is not a problem because the values \u200b\u200bresult really good!

They told me that maybe it was the router or modem, but I do not believe it because it has always worked well ... I also did the firmware update but the problem is always the same. And then I keep getting crap in the lobby, and the ping dns works!

If it were the fault of the modem, how do you explain the fact that I keep getting the crap into, and be able to get responses to ping and DNS?

However in the end I managed to find a small solution.

I set the router to BRIDGED mode. I can make the PPPoE connection to my OpenBSD gateway and I wrote a little cron script every 3 minutes ago pinging Google.

This trick seems to work great, and the connection can remain active for several days without ever giving problems ...

I hope that this information can help someone.

Sunday, May 6, 2007

Msx 2 Roms Metal Gear (u)

OpenBSD 4.0 e filesystem /home criptato

Post updated.

After endless searching with Google, many failed experiments and various incazzature, I managed to create a filesystem / home encrypted on OpenBSD 4.0 without the use of particular programs, but with only the tools in the system.

The steps work properly with a partition 3GiB. Some guides report that the device can not exceed snvd the size of 8GiB. From some tests I made I would say that they are wrong. I assume that this procedure will work with higher dimensions, but is not guaranteed. If you have a way to test different configurations, please let me know.

The partition is to be encrypted / home and corresponds to the BSD partition 'g'. Adapt to suit your needs.

Start by installing OpenBSD as usual. You create all the partitions as you need as /, / tmp, / var, / usr, and of course a separate / home.

 Example: 16 partitions: # size offset fstype [fsize bsize cpg] a: 262017 63 4.2BSD 2048 16384 260 # Cyl 0 *- 259 b: 524160 262080 swap # Cyl 260 to 779 c: 19541088 0 unused 0 0 # Cyl 0 to 19,385 d: 262080 786240 4.2BSD 2048 16384 260 # Cyl 780-1039 e: 262080 1048320 4.2BSD 2048 16384 260 # Cyl 1040 to 1299 f: 12582864 1310400 4.2BSD 2048 16384 328 # Cyl 1300 to 13782 g: 5641776 13893264 4.2BSD 2048 16384 328 # Cyl 13783 to 19379 

ends the installation and restart the system.

Now, when you are ready to start the `process` to encrypt the / home partition, it must first be removed; and then you have to work as `root` and `normal 'people can not be logged into the system.
addition, the file `/ etc / fstab 'should not contain more than the line that automatically mounts / dev/wd0g in / home.

 # umount / home # dd if = / dev / zero of = / dev/wd0g bs = 1k 

At this point the partition is associated to a device `g` `` snvd0.

 # vnconfig snvd0-k / dev/wd0g Encryption key: 

will be prompted to enter your password. MUST BE VERY CAREFUL as it can be entered only once A ! Do not miss the next association as only you can `scoprire` che la password era sbagliata...



A questo punto si deve configurare il dispositivo "virtuale" come se fosse un disco. Lo si deve `configurare` in modo che contenga due partizione: `a` e `c`. Entrambe devono avere la stessa dimensione della partizione `reale` `g`. `c` è di tipo `unused`, mentre `a` è di tipo 4.2BSD. Il risultato deve essere come nell'esempio:



 # disklabel -E svnd0
disklabel: Can't get bios geometry: Device not configured

Initial label editor (enter '?' for help at any prompt)
> p
16 partitions:
# size offset fstype [fsize bsize cpg]
a: 5641776 0 4.2BSD ...
c: 5641776 0 unused ...

Now, you can format the partition `a`:

 # newfs / dev/svnd0a 

and is mounted on / home: # mount-o

 softdep, nodev, nosuid / dev/svnd0a / home 

The system is now ready for use. Note that all that is written to / home, it is actually written to the partition using the `g` `cipher blowfish`.

If you were to reboot the system, it shall automatically be stripped of the partition. However, when it will return `active`, the / home partition is not mounted. `` To activate it do the following:

# K-
 vnconfig svnd0 / dev/wd0g Encryption key: 

and type the correct password.
Now you can reassemble and check that the password is correct: # mount-o

 softdep, nodev, nosuid / dev/svnd0a / home 

If the system were to make a mistake and say that the partition contains a fs FFS, it means that the password is incorrect.

If all goes well, you can enjoy the / home partition encrypted!

Friday, May 4, 2007

Celica Immobiliser Fault

Vpn tramite ssh

The post has been modified to include a number of improvements.

From the series "ssh resources are endless," I present a little known feature of ssh to create VPN.
The information contained herein is an OpenBSD server and client Ubuntu Linux, but adapting them can be extended to any configuration.

In OpenSSH, for some time, we've included support for VPN tunneling using the pseudo-network device tun (available on many platforms).

The first step is enabled in the OpenSSH server activation request of the tunnel by the client and ensure that the only command that the client can do is to activate the device tun server
To do this Just add the following options in the configuration file (/ etc / ssh / sshd_config):

 ... PermitTunnel point-to-point PermitRootLogin forced-commands-only ... 

and restart the server by using the hangup signal.
See the manual the meaning of these parameters and the various other possible configurations.

Then, to authenticate the client without using passwords, and force him to run only the command to activate the tunnel, you can use public key authentication provided by OpenSSH.
Edit the file / root / .ssh / authorized_keys to contain a line like:

 tunnel = "0" command = "sh / etc / netstart tun0" ssh-rsa ... utente@macchina.dominio 

where the second space is the user's public key that is to trigger the tunnel.

this is done, all that remains is to configure the local interface tun0 is an address assigning.
On OpenBSD this work is done by providing the file hostname.if, in which `if` is the name of the device.
In our case we need to create a file from the content hostname.tun0:

 inet 192.168.0.9 dest 192.168.0.10 255 255 255 252 NONE 

interface that assigns the address 192.168.0.9 and expects the other end there is 192.168.0.10.
(In my LAN I have used these addresses and subnetting are among the free ones).

remains now is to configure the client.
By assumption, the activation of the VPN tunnel on the client will be done by root. using sudo, however you can launch the vpn activation by non-privileged user.
First, you decide the number of the tun device to use. (In the example, the client is used tun0).

client is configured by placing the configuration file / root / .ssh / config so that it contains:

 Host vpn tunnel yes Hostname server.domain TunnelDevice 0: any User root 

Furthermore, we must prepare the script `` enable_tunnel which has the task of giving is an address to the tun0 interface and set the routing table to reach the private LAN.
Remember that the address to be assigned in this case it is 192.168.0.10, and the remote is 192.168.0.9

Create a script in / root / bin / enable_tunnel the content:

 # / bin / sh ifconfig tun0 192.168.0.10 netmask 255,255,255,252 pointopoint 192.168.0.9 route add-net xxxx netmask 192.168.0.9 gw 

YYYY where XXXX and YYYY specifies the network address and netmask of the network that is `behind` the OpenSSH server.

Now, to ensure that normal users can activate the VPN, you need to configure sudo so that it can run the command: $ ssh-f

 vpn true & & sh / root / bin / enable_tunnel 

I solved the problem by creating an alias in your bash called vpn.

From this moment you can access the private network as if they were connected into it and, symmetrically, it can be accessed from it!

To end the VPN just kill the ssh process. PS

the VPN works even if you are behind a proxy server http / https. In order for this to happen, we must also enable the SSH server on port 443.
Also, install a program such as `connect-proxy 'on the client, and modify the configuration as:

 Host ProtocolKeepAlives 30 ProxyCommand vpn-proxy-connect proxy-H ABCD: 3128 443 server.domain Tunnel yes TunnelDevice 0: any User root 

Where ABCD: 3128 is the proxy server address and 3128 is the proxy port (usually squid).
The VPN works the same as above! In practice, it asks the server proxy `` put in contact with the door 443 of the SSH server. The proxy allows him to think that because we are using SSL. Instead, we're going to use SSH.

Wednesday, May 2, 2007

Four Poster Canopy Bed Plans

Ubuntu Stickers!

This morning I got two stickers "Powered by Ubuntu Linux" that I had requested last week!

What about ... are truly beautiful and make their shape! I have

messo uno sul portatile, ed uno sul desktop. Ora sono proprio personalizzati.





Per chi è interessato, può leggere come fare ad ottenerli tramite questo link .



Per un utente Ubuntu convinto, credo che questi siano un "must".




Wednesday, April 25, 2007

9 Weeks Pregnant Cervix Still Very Low

Login grafico via ssh


Le risorse di ssh sono infinite!



La cosa più semplice che ssh permette di fare è l'accesso ad una macchina remota e l'impartire comandi da CLI come se si fosse fisicamente di fronte ad essa.



Alcune volte, però, mi sarebbe stato più utile avere un accesso di tipo grafico su quella macchina.



I searched google and found information with XDMCP, a protocol that is already available in Ubuntu's GDM and of course ... (But also other Unix)

This, however, is a protocol that encrypts the traffic and consequence of a solution is not very safe to use on the Internet!

After exhausting research, I found a solution that makes efficient use of ssh to encrypt the data and an X server like Xnest or Xephyr.

Then, on the target machine must be installed in addition to the OpenSSH server Xephyr server (or Xnest).

Then, to get a graphical login on that machine just log in via ssh enabling X11 forwarding with: $ ssh-X remote-host

 
and then run:
 $ xinit / etc/X11/xinit/xinitrc - / usr / bin / Xephyr: 1-
800x600 screen which will open a window on the host by which we are connected inside the graphic session ... And then you can use the target machine with a GUI as if you were in front of it!

In my case, you start a GNOME session that keeps all your settings and preferences saved on the remote machine.

Here is a picture that gives an idea of \u200b\u200bhow things work ...

Saturday, April 21, 2007

Masterbation In Restroom

Ubuntu 7.04 fantastica!

I was molto colpito dall'ultima versione di Ubuntu 7.04: Feisty Fawn!



Devo dire che è l'ennesimo grandissimo balzo in avanti in campo informatico effettuato dalla comunità del Software Libero!



L'installazione è fantastica, la gestione dell'hardware meravigliosa, la semplicità d'uso spettacolare e la possibilità di personalizzazione celestiale.



Dopo aver installato il sistema, al riavvio funziona tutto bene.



La cosa che mi piace tantissimo di Ubuntu è che dopo che l'installazione è terminata, al riavvio della macchina essa è già pronta all'uso per un buon numero di casi tipici (tra cui i miei)!

In pratica non mi fa perdere additional time with the action of boring having to reinstall all the programs I need (such as Debian or the award-winning Windows). Then, not making me
annoys me to find several gigabytes of software that does not use! (Such as Suse or Fedora)
These choices were made by the Ubuntu team have made it my operating system "standard."

Then, for those who desire and time to refine the configurations can do so (even though it was edited it all in detail, and then just a few clicks to disable only the services that are not needed).

Now a question springs to mind ... Why people spend a lot of money on Windows Vista or aggiornare Mac OS piuttosto che usare un sistema operativo decente basato su Linux come Ubuntu (e fare una donazione di qualche decina di €)?


Thursday, April 19, 2007

How To Clean Flame Sensor

FON: vai avanti così!


Mi sono dovuto ricredere. Le lamentele del vecchio post sono diventate in parte obsolete da quando FON ha cambiato la politica di gestione degli account.



Ora, chi non condivide l'ADSL per un periodo di tempo stabilito (30 giorni), viene classificato come utente che non "mantiene la promessa fatta" e come conseguenza gli viene disattivato l'account.



Questa mi sembra un'ottima trovata per evitare che la gente se ne approfitti dell'ADSL degli altri.



Secondo me, comunque, account management should be further enhanced. For example, 30 days seems to me too .... Better a week! Or maybe use an algorithm that takes into account the earlier days of sharing, so if one goes on vacation and shared throughout the year, he is given a much longer period of time ....

also remain of the view that traffic should be logged, that FON needs to pass the traffic from its proxy that filters some sites and that every user must provide personal documents relevant to the intrinsic safety of the project.

conclude, I am very happy with the new Fonero Gets Fonero policy with which, now, a Fonero may be at a price of Sussudio to the Fonera his friend outside the community.

The idea of \u200b\u200bthe first, in which the fonera was "entirely donated," she was beautiful, but you know, there are the usual sharpers that if they always take advantage ... I should thank them for that change.

On some sites I've seen people with 5 or 6 Fonera on which were the "experiments". My disdain goes to them because they have taken away to people who could keep his word! (At least they could do in order to take 3 or 4 to share the ADSL and pick 1 or 2 to "play"!)

PS I have 3 calls for "Fonero Gets Fonero". If anyone is interested in having the Fonera for € 20, including shipping, can contact me by email.

Thursday, February 8, 2007

Creative Sound Blaster Ct4780 Driver For Xp

La Fonera parte 3

Joining the FON community means sharing your ADSL.
I strongly agree with this idea. However, since the line is mine, and I Fonera paid , pretend to decide what and when share.

The "how" you can determine the user's homepage limiting the speed limit for the public network.
The "when" you can not decide.

I think you have to leave you to decide. It 's a community this or not? Not to be trusted each other?

not find the right Foneros we should trust each other, but that does not trust the Foneros FON!

The concept is this: I am a Fonero I trust the other Foneros. I have to trust the fact that they are not to use my connection for illegal purposes. I have to trust that you do not use my connection for visiting child porn websites. In these cases I'd be responsible. These things are very serious, but I have to trust.

just can not find, however, that FON does not trust me. I have sold a router "locked" so that I always agree with must and my band. Because I

that at risk "severe" I trust the other and they do not trust me? This

not find a correct policy.

I am willing to share my band. But I want guarantees. Fon And not many guarantees in this regard.
may change the registration system: a Fonero must provide a photocopy of the identity authenticated in any way (it becomes legal in Italy).
could change the login system to monitor traffic or something like that ... And so on.

Fon is a company. And as such, going forward, should be done with profits. It must decide how to spend money.

I believe that the first expense to be done increase the safety of Foneros. FON but prefers to spend money on advertising and to create new "useless" ... (See the fonera 2.0)

We are a community. So if I have to trust the other Foneros, FON has to trust first for me.

below instead of information that might be useful to someone.
not stretch how to build a serial adapter, go to the Fonera via a serial or anything like that. The Web is full of these documents and google was born for that.

FONERA BOOT OF A VIRGIN:

 + PHY ID is 0022:5521 Ethernet eth0: MAC address XX: XX: XX: XX: XX: XX IP: 0.0.0.0/255.255.255.255,  Gateway: 0.0.0.0
Default server: 0.0.0.0

RedBoot(tm) bootstrap and debug environment [ROMRAM]
Non-certified release, version v1.3.0 - built 16:57:58, Aug 7 2006

Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.


Board: ap51
RAM: 0x80000000-0x81000000, [0x80040450-0x80fe1000] available
FLASH: 0xa8000000 - 0xa87f0000, 128 blocks of 0x00010000 bytes each.
== Executing boot script in 1.000 seconds - enter ^C to abort



RIPRISTINARE LA CONFIGURAZIONE REDBOOT ORIGINALE:

 
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>> fis load -l vmlinux.bin.l7
>> exec>> Boot script timeout (1000ms resolution): 1 Use BOOTP for network configuration: false Gateway IP address: 0.0.0.0 Local IP address: 0.0.0.0 Local IP address mask: 255.255.255.255 Default server IP address: 0.0.0.0 Console baud rate: 9600 GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Update RedBoot non-volatile configuration - continue (y / n)? y ... Erase from 0xa87e0000-0xa87f0000:. ... Program from 0x81000000-0x80ff0000 0xa87e0000 at:. RedBoot>

PARTITIONS OF A VIRGIN FONERA 0.7.1.2:

 RedBoot> fis list Name FLASH addr Mem addr Length Entry point RedBoot 0xA8000000 0xA8000000 0x00030000 0x00000000 0x00700000 0x00000000 rootfs 0xA8030000 0xA8030000 vmlinux.bin.l7 0xA8730000 0x000B0000 0x80041000 FIS directory 0x80041000 0x00000000 RedBoot config 0x0000F000 0xA87E0000 0xA87E0000 0xA87EF000 0xA87EF000 0x00001000 0x00000000 

0.7.1.2 extract the firmware from the archive. FON: $ dd if =

 fonera_0.7.1.2.fon fonera.tar.gz of = bs = 519 skip = $ 1 tar xzvf fonera.tar.gz 

Reload firmware 0.7.1.2 ORIGINAL (TESTED WITH TFTP DOES NOT WORK WITH XMODEM):

 RedBoot> ip_address-l-h 192.168.xx 192.168.XX/24 / * set the local ip-l,-h sets the ip tftpd server * / RedBoot> fis init RedBoot> load-r-b 0x80040450 rootfs.squashfs RedBoot> fis create-b 0x80040450-f 0xA8030000-l 0x00700000-e 0x00000000 rootfs RedBoot> load-r-b% {kernel} FREEMEMLO. lzma RedBoot> fis create-r 0x80041000-e 0x80041000 vmlinux.bin.l7 RedBoot> fis load-l vmlinux.bin.l7 RedBoot> exec 

SSH daemon PERMANENT:

 root @ OpenWrt: ~ # mv / etc / init. d / dropbear / etc/init.d/S50dropbear root @ OpenWrt: ~ # cp / etc / firewall.user / etc / firewall.user.orig root @ OpenWrt: ~ # chmod-wx / etc / root firewall.user.orig @ OpenWrt: ~ # echo "iptables-t nat-A prerouting_rule-i $ WAN \\-p tcp - dport 22-j ACCEPT ">> / etc / firewall.user root @ OpenWrt: ~ # echo" iptables-A input_rule-i $ WAN \\-p tcp - dport 22-j ACCEPT ">> / etc / root firewall.user @ OpenWrt: ~ # reboot 

gain control over his FONERA:

 root @ OpenWrt: ~ # cp / bin / thinclient / bin / thinclient.orig root @ OpenWrt: ~ # chmod-wx / bin / Change the thinclient.orig 'last line of file / bin / thinclient. / Tmp / .thinclient.sh "to" mv / tmp / .thinclient.sh / tmp/thinclient.sh- $ (date '+% Y% m% d-% H% M') "

DECIDE WHEN SHARING ADSL:

 # / bin / sh # # / bin / nofon # case "$ 1" in up) (up & & ifconfig tun0 ifconfig ath0 up & & \\ echo "Fon network is up!")  file_copiato 

WIRELESS CONTROL SIGNAL:

 root @ OpenWrt: ~ # iwlist ath0 tx ath0 8 available transmit-powers ": 0 dBm (1 mW) 6 dBm (3 mW) 8 dBm (6 mW) 10 dBm (10 mW) 12 dBm (15 mW) 14 dBm (25 mW) 16 dBm (39 mW) 18 dBm (63 mW) Current Tx-Power = 18 dBm (63 mW) root @ OpenWrt: ~ # iwconfig ATH1 txpower Xdbm / * X can vary from 1 to 18. Value must be added to the power antenna 2dBm. * / 

 

Monday, January 29, 2007

Sasuke And Sakura Lemons Story

Donazione per software libero

the OpenBSD project and some euro via paypal to Ubuntu Linux.

The question that led me to this act is "why should I pay hundreds of euro to the poor software and good software for nothing?

Although the offer is very small I think the gesture is worth a lot.

I hope that readers of this blog devolvino to charity some € for the project that is closest to his heart (if they have not already).

I think that no matter how it allocates, but those who make this gesture ...

Monday, January 15, 2007

Sample Welcome New Client Letter

Asus WL-167G hack

This device is the "virgin".

Once unsolder the antenna (the blue piece), the adapter must be welded as shown: the mass goes up, the antenna goes under. The result should look like this:

I put hot glue to hold the wire securely attached by welding. is the result:

Now the scope is fantastic. I can also "catch" signals very far away.

Wednesday, January 10, 2007

Lakedew Harlur Main Road

La Fonera parte 2

not that I owned and registered in the past, but an entirely new object.

Evidently they preferred to send me a new Fonera rather than repair the one I had before.

I reconnected all the cables and I recorded this new trinket.

This time I'm very happy that everything worked perfectly and wi-fi is fantastic: I covered the whole apartment and I noticed that "goes outside" ...

;-) I think this project is really something new for me and for those equipped with a laptop, it's worth joining the FON Community.

damn I love the philosophy of "peer to peer": "I do something to you and you, in return, will the one to me."

Here is some information that might be useful. If you are unable to access via wi-fi to the Fonera, you must connect your laptop to the same segment of network (wired) La Fonera and change the IP address in 169.254.255.2/255.255.255.0. (You can also use a cross cable between laptop and Fonera).

pointing your browser to 169.254.255.1 to access the control panel and you can change the settings as required. It occurred to me that

using the default channel 1 of the wi-fi network, the signal was a little bit intermittent. Putting it on channel 11 the problem disappears and the signal becomes very stable.

I believe this is due to interference with some unknown to me.