Re: [freenet-support] In need of opinions and ideas
snip Anyway, long live king bush Has anyone figured out what he had for lunch. The schmerk is almost missing in his salute picture in the USA Today shot by AFP. Does that stand for Air Force Photograph. I didn't say gone, just almost missing. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Re: Why Freenet doesn't try any nodes?
Nick Tarleton schrieb: I've started using Freenet for the Nth time (transient - 5084 - WinXP - Sun JVM 1.4.1), and am going through the 99% RNF phase. I know this is normal, but I noticed that many of them RNF instantly and say no nodes were tried. If it's not too hard to explain, I'd like to know the reason for this. Why is it not even trying - sometimes for 5 times in a row - to request what I tell it to? Maybe because the network is getting something like a mini reset due the fact that 5085 is out, and it contains quite a bit of changes to the routing alg. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Load
David Masover wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Toad wrote: | No, if you can do that, then you can portscan for Freenet nodes. That's | a REALLY bad idea. You need to use some sort of seednodes mechanism. Why is that a bad idea? If a government is paranoid enough, they can just put devices all over which block any crypted traffic. Some sort of way for an effective seednodes file to be chosen or built quickly, then. |Obviously clients should be able to override that, but I think that fast |node connection is feasable, if The Network (TM) was fast enough. | | | Maybe so. But we want them to be USEFUL to the network. That won't | happen if they're only up for 5 minutes. They are useful if they make it more popular. Suppose there is some lag, say, 30 seconds to a minute to get an effective seednodes.ref. On top of that, such a node probably wouldn't be able to have a terribly big cache. Then there's incentive for people to whine for permanent nodes, and it wouldn't be too long before these Public Access Internet Terminals (or whatever hype word they use now) start being preloaded with Freenet. When governments gets involved in censorship, it is not usually that they are paranoid, but that they want the power to control. Sometimes to control the masses, but more often just to control the unloyal opposition, or those who simply disagree with them. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] [Fwd: Stable build 5085 - please upgrade]
Seems like this didn't make it here. Check the devel or technical list if you don't trust me. Original-Nachricht Betreff: Stable build 5085 - please upgrade Datum: Thu, 22 Jul 2004 18:55:40 +0100 Von: Toad [EMAIL PROTECTED] Antwort an: Discussion of development issues [EMAIL PROTECTED] Newsgroups: gmane.network.freenet.devel,gmane.network.freenet.technical Freenet stable build 5085 is now available. Please upgrade ASAP, if you are running a stable branch node (if you are running unstable, you'll know that you're running unstable). You can do this using the update.sh script on POSIX-like systems such as Linux and MacOS/X (or Darwin): ./stop-freenet.sh ./update.sh ./start-freenet.sh On Windows, you can use the update option on the start menu. On any platform, you can stop the node, download http://freenetproject.org/snapshots/freenet-latest.jar over your existing freenet.jar, and then start the node up again. Note that this build makes 5084 mandatory, so if you are still running 5083, you should DEFINITELY upgrade. This is the result of more than 2 months work, and has many changes: Some major changes to a critical part of the routing algorithm, the KeyspaceEstimators. The new implementation is faster and much more accurate. There are also many other changes to the routing code. There may be a readjustment period on the network for a while as people upgrade and the network sorts itself out. Your routing table will be reset on upgrade: the nodes will still be there but because of the algorithm change, the node will need to discover what their specialities are all over again. Sorry, it was not possible to make this backwards compatible. Many other minor routing improvements, many of them as a result of simulation (by running several nodes simultaneously on one machine, and running tests). Firewalled nodes will now automatically pick up their IP address from the nodes they are connected to (once enough nodes have upgraded). Thus you no longer need to specify an address in the config file or use dyndns. This should make Freenet significantly easier to use for new users on firewalled/NATted setups. You will still need to forward the listenPort for maximum performance as we have not yet implemented automatic port forwarding (it would require us to borrow some code for Universal Plug and Play from other GPL'd Java apps; we may do this later). Several fairly significant rate limiting fixes and improvements. Nodes were comparing two averages over different time periods when calculating their current request capacity, and sending the wrong Minimum Request Interval to the requesting node. This caused significant problems in our simulations. Also we now send keepalive messages occasionally, including the MRI, so that nodes don't get out of date when the MRI changes quickly (for example on startup). Fixed a number of long running bugs affecting inserts, mostly at the client end. Especially inserts of large files. If you gave up trying to insert something because of timeouts, try it again on 5085. Use a limit of 80 connections by default on Windows 98/ME, not 40. This should make nodes on such operating systems work slightly better. If you have problems with running out of sockets you may need to reduce the limits. New diagnostics, new scripts, updates to scripts, improvements to announcements (but still not working properly), fixes for NullPointerExceptions (if you don't know what these are you don't want to), improvements to the routing table status pages, always overwrite the old logfile unless told otherwise in the config file (logOverwrite) to prevent the disk filling up, two new stats, node_number renamed to node, and loads of internal refactoring (moving code around, deleting dead code). -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: PGP signature ___ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] New distribution
For the first time in several months I'm getting modifiers on the icons of inbound outbound. Number of requests (sent/received) 1902/6872 Type Peer Messages Queue Datatransferred Idletime Lifetime 130.83.163.154:21507 99:22 - 6,830Bytes 21 s 48:10 140.247.204.34:1789 201:190 - 190KiB 22 s 47:49 p2p.dyndns.info:9500 122:575 - 525KiB 6 s 47:48 benedikt.dyndns.info:62085 93:65 - 8,023Bytes 5 s 46:57 66.26.77.109:6887 123:253 - 212KiB 21 s 46:35 193.205.163.168:33158 177:107 - 67KiB 14 s 46:29 24.158.21.13:46696 1159:858 - 380KiB 0 s 46:28 69.50.242.114:25082 157:199 - 164KiB 0 s 46:23 phisatho.homeip.net:9822 1124:597 - 243KiB 6 s 46:19 freehost.dnsalias.org:9818 96:241 - 193KiB 1 s 46:16 82.182.97.195:29003 106:39 - 12KiB 32 s 46:09 67.100.90.41:13235 96:16 - 6,742Bytes 39 s 46:07 134.147.128.177:17869 88:8 - 4,285Bytes 1:02 45:38 eckmail.dyndns.org:5 87:14 - 5,078Bytes 30 s 45:29 68.187.117.4:56722 87:12 - 5,067Bytes 4 s 45:06 69.3.61.165:40736 90:53 - 14KiB 12 s 43:23 24.168.168.234:61380 1819:668 - 679KiB 0 s 43:18 wasitbill.truthhides.com:37920 1073:622 - 261KiB 1 s 43:09 myaddress.mine.nu:43188 212:306 - 267KiB 6 s 38:13 no addresses 6557:3544 - 1,945KiB 0 s 37:34 81.86.79.102:45251 326:290 - 186KiB 0 s 37:31 217.112.178.6:25845 :905 - 494KiB 0 s 37:29 24.0.237.164:54260 1578:1136 - 570KiB 0 s 34:46 81.57.93.31:15212 2203:1130 - 643KiB 0 s 34:00 sadpony.homedns.org:23233 458:1300 - 773KiB 10 s 30:46 24.88.102.148:47773 202:143 - 41KiB 0 s 9:47 red5.mine.nu:24698 40:26 - 13KiB 0 s 2:07 inline: arrow_inbound_sleeping.pnginline: arrow_outbound_sleeping.pnginline: arrow_inbound_transmitting.pnginline: arrow_outbound_transmitting.png___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] In need of opinions and ideas
Nicholas Sturm wrote: Has anyone figured out what he had for lunch. The schmerk is almost missing in his salute picture in the USA Today shot by AFP. Does that stand for Air Force Photograph. I didn't say gone, just almost missing. What's a schmerk? Agence France Presse. Z -- Framtiden är som en babianröv, färggrann och full av skit. Arne Anka ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Sorry if any of those was too large. Feel free to kill as much as desired.
Null. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] In need of opinions and ideas
Sorry, local Americanism, I guess. If is a smile that has an artificial appearance because the corner of the mouth don't seem to know where they should be. Usually carries a derogatory implication to the observer, perhaps forced grim would carry the idea. -- Sorry. Zenon Panoussis wrote: Nicholas Sturm wrote: Has anyone figured out what he had for lunch. The schmerk is almost missing in his salute picture in the USA Today shot by AFP. Does that stand for Air Force Photograph. I didn't say gone, just almost missing. What's a schmerk? Agence France Presse. Z ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Weird Error
Probably a hardware problem. Is it overheating? On Thu, Jul 22, 2004 at 05:58:26PM -0700, Shoey Fighter wrote: Hello. I have recently installed Slackware 10.0 (java 1.4.2) and the latest stable build of Freenet. It worked seemingly fine for a few days, but then after letting it go by itself for a while I noticed my router wasn't showing much activity. I logged in via SSH, only to find that the service was no longer going. Confused, I started it again, and this time left the console window open to see if anything would be dumped. Eventually, the following message was dumped. (The only settings I changed in my configuration are allowedhosts=all computers on my network, maxconnections=150, ipaddress=mine, logfile=error, datastoresize=5000M). Now it takes about half of an hour (or less) for this error to come up. Any suggestions would be greatly appreciated. I can also include my configuration or any other info you might need. Thanks, ShoeyFighter Message: == Unexpected Signal : 11 occurred at PC=0x4031DF3A Function=(null)+0x4031DF3A Library=/usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.Object.wait(Native Method) - waiting on 0x45e88ee8 (a java.lang.Thread) at java.lang.Thread.join(Thread.java:1001) - locked 0x45e88ee8 (a java.lang.Thread) at java.lang.Thread.join(Thread.java:1054) at freenet.Core.join(Core.java:539) at freenet.node.Main.main(Main.java:1016) Dynamic libraries: 08048000-0804e000 r-xp 03:02 33051 /usr/lib/j2sdk1.4.2_04/bin/java 0804e000-0804f000 rw-p 5000 03:02 33051 /usr/lib/j2sdk1.4.2_04/bin/java 4000-40014000 r-xp 03:02 12031 /lib/ld-2.3.2.so 40014000-40015000 rw-p 00013000 03:02 12031 /lib/ld-2.3.2.so 40016000-4001e000 r-xp 03:02 33532 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/native_threads /libhpi.so 4001e000-4001f000 rw-p 7000 03:02 33532 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/native_threads /libhpi.so 4001f000-40029000 r-xp 03:02 12071 /lib/libnss_compat-2.3.2.so 40029000-4002a000 rw-p 9000 03:02 12071 /lib/libnss_compat-2.3.2.so 4002c000-4003a000 r-xp 03:02 12078 /lib/libpthread-0.10.so 4003a000-4003b000 rw-p e000 03:02 12078 /lib/libpthread-0.10.so 4007d000-4007f000 r-xp 03:02 12067 /lib/libdl-2.3.2.so 4007f000-4008 rw-p 1000 03:02 12067 /lib/libdl-2.3.2.so 4008-401a8000 r-xp 03:02 12065 /lib/libc-2.3.2.so 401a8000-401ac000 rw-p 00128000 03:02 12065 /lib/libc-2.3.2.so 401b-405ab000 r-xp 03:02 33536 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm. so 405ab000-405c6000 rw-p 003fa000 03:02 33536 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm. so 405d9000-405eb000 r-xp 03:02 12070 /lib/libnsl-2.3.2.so 405eb000-405ec000 rw-p 00011000 03:02 12070 /lib/libnsl-2.3.2.so 405ee000-4060f000 r-xp 03:02 12068 /lib/libm-2.3.2.so 4060f000-4061 rw-p 0002 03:02 12068 /lib/libm-2.3.2.so 4061-40614000 rw-s 03:02 191373 /tmp/hsperfdata_root/1286 40614000-40624000 r-xp 03:02 33525 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libverify.so 40624000-40626000 rw-p f000 03:02 33525 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libverify.so 40626000-40646000 r-xp 03:02 33540 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libjava.so 40646000-40648000 rw-p 0001f000 03:02 33540 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libjava.so 40648000-4065c000 r-xp 03:02 33530 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libzip.so 4065c000-4065f000 rw-p 00013000 03:02 33530 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libzip.so 4065f000-41fff000 r--s 03:02 33646 /usr/lib/j2sdk1.4.2_04/jre/lib/rt.jar 42049000-4205f000 r--s 03:02 33605 /usr/lib/j2sdk1.4.2_04/jre/lib/sunrsasign.jar 4205f000-4213a000 r--s 03:02 33582 /usr/lib/j2sdk1.4.2_04/jre/lib/jsse.jar 4213a000-4214b000 r--s 03:02 33652 /usr/lib/j2sdk1.4.2_04/jre/lib/jce.jar 4214b000-426a4000 r--s 03:02 33644 /usr/lib/j2sdk1.4.2_04/jre/lib/charsets.jar 4474c000-4474f000 r--s 03:02 33516 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/dnsns.jar 5080e000-5083a000 r--p 03:02 62976 /usr/lib/locale/en_US/LC_CTYPE 5083a000-50856000 r--s 03:02 33517 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/sunjce_provider .jar 50856000-50863000 r--s 03:02 33518 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/ldapsec.jar 50863000-5091f000 r--s 03:02 33519 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/localedata.jar 5091f000-50b57000
Re: [freenet-support] Why Freenet doesn't try any nodes?
Because all the nodes are backed off. If you upgrade to 5085 this will be clearer. On Thu, Jul 22, 2004 at 11:36:08PM -0400, Nick Tarleton wrote: I've started using Freenet for the Nth time (transient - 5084 - WinXP - Sun JVM 1.4.1), and am going through the 99% RNF phase. I know this is normal, but I noticed that many of them RNF instantly and say no nodes were tried. If it's not too hard to explain, I'd like to know the reason for this. Why is it not even trying - sometimes for 5 times in a row - to request what I tell it to? -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] [Tech] Stable build 5085 - please upgrade
Freenet stable build 5085 is now available. Please upgrade ASAP, if you are running a stable branch node (if you are running unstable, you'll know that you're running unstable). You can do this using the update.sh script on POSIX-like systems such as Linux and MacOS/X (or Darwin): ./stop-freenet.sh ./update.sh ./start-freenet.sh On Windows, you can use the update option on the start menu. On any platform, you can stop the node, download http://freenetproject.org/snapshots/freenet-latest.jar over your existing freenet.jar, and then start the node up again. Note that this build makes 5084 mandatory, so if you are still running 5083, you should DEFINITELY upgrade. This is the result of more than 2 months work, and has many changes: Some major changes to a critical part of the routing algorithm, the KeyspaceEstimators. The new implementation is faster and much more accurate. There are also many other changes to the routing code. There may be a readjustment period on the network for a while as people upgrade and the network sorts itself out. Your routing table will be reset on upgrade: the nodes will still be there but because of the algorithm change, the node will need to discover what their specialities are all over again. Sorry, it was not possible to make this backwards compatible. Many other minor routing improvements, many of them as a result of simulation (by running several nodes simultaneously on one machine, and running tests). Firewalled nodes will now automatically pick up their IP address from the nodes they are connected to (once enough nodes have upgraded). Thus you no longer need to specify an address in the config file or use dyndns. This should make Freenet significantly easier to use for new users on firewalled/NATted setups. You will still need to forward the listenPort for maximum performance as we have not yet implemented automatic port forwarding (it would require us to borrow some code for Universal Plug and Play from other GPL'd Java apps; we may do this later). Several fairly significant rate limiting fixes and improvements. Nodes were comparing two averages over different time periods when calculating their current request capacity, and sending the wrong Minimum Request Interval to the requesting node. This caused significant problems in our simulations. Also we now send keepalive messages occasionally, including the MRI, so that nodes don't get out of date when the MRI changes quickly (for example on startup). Fixed a number of long running bugs affecting inserts, mostly at the client end. Especially inserts of large files. If you gave up trying to insert something because of timeouts, try it again on 5085. Use a limit of 80 connections by default on Windows 98/ME, not 40. This should make nodes on such operating systems work slightly better. If you have problems with running out of sockets you may need to reduce the limits. New diagnostics, new scripts, updates to scripts, improvements to announcements (but still not working properly), fixes for NullPointerExceptions (if you don't know what these are you don't want to), improvements to the routing table status pages, always overwrite the old logfile unless told otherwise in the config file (logOverwrite) to prevent the disk filling up, two new stats, node_number renamed to node, and loads of internal refactoring (moving code around, deleting dead code). -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Tech mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/tech___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] More outtakes
Smoothed local mean traffic (queries per hour): 9352.503 Smoothing half life (lsHalfLifeHours): 1.200 hour. That is, the rate decays completely to a new value after 12.000 hour. Instantaneous local traffic: 5541.582 queries per hour. That is, the last 500 queries arrived in 324.817 second or 0.090 hour. Current proportion of requests being accepted: 1.000 Current advertise probability: 0.029 Traffic data from 100 nodes (max allowed 100), of which 85 were used. The oldest 5% and the smallest and largest 5% (up to 10% if the table is not full) are not used in computing statistics. Global mean traffic per node (queries per hour): 5453.235 Global median traffic per node (queries per hour): 3824.000 Standard Deviation of global traffic per node: 4290.161 Uptime: 0 days, 0 hours, 57 minutes Current routingTime: 0ms. Pooled threads running jobs: 18 (15%) Pooled threads which are idle: 21 Current estimated load for rate limiting: 15%. Load due to thread limit = 15% Load due to routingTime = 10% = 100ms / 1000ms = overloadLow (100%) Load due to messageSendTimeRequest = 11.8% = 118ms / 1000ms = overloadLow (100%) Load due to output bandwidth limiting = 6.5% because outputBytes(38308) = limit (589824.009 ) = outLimitCutoff (0.8) * outputBandwidthLimit (12288) * 60 Load due to expected inbound transfers: 0.5% because: 3070.2743633516343 req/hr * 0.002732390326442652 (pTransfer) * 121167.0 bytes = 1016492 bytes/hr expected from current requests, but maxInputBytes/minute = 2949120 (output limit assumed smaller than input capacity) * 60 * 1.1 = 194641920 bytes/hr target Current estimated load for QueryRejecting: 15%. Architecture and Operating System Architecture x86 Available processors 1 Operating System Windows 2000 OS Version 5.0 Java Virtual Machine JVM Vendor Sun Microsystems Inc. JVM Name Java HotSpot(TM) Client VM JVM Version 1.4.2_05-b04 Memory Allocation Maximum memory the JVM will allocate 130,112 KiB Memory currently allocated by the JVM 25,344 KiB Memory in use 21,822,432 Bytes Estimated memory used by logger None Unused allocated memory 4,127,928 Bytes Data Store Maximum size 376 MiB Used space 381,608 KiB Free space 3,416 KiB Percent used 99 Total keys 3225 Space used by temp files 7,776 KiB Maximum space for temp files 131,421,529 Bytes Most recent file access time Fri Jul 23 05:12:05 EDT 2004 Least recent file access time Tue May 11 05:24:40 EDT 2004 Transports Current IPv4 address 63.191.136.113 Current IPv4 port 49980 ARK sequence number 123 Last ARK sequence number inserted 122
Re: [freenet-support] Unknown Exception (support@freenetproject.org)
AAARGH. Sorry, deceived by the subject line. On Fri, Jul 23, 2004 at 09:35:10AM +0200, [EMAIL PROTECTED] wrote: Mail Delivery - This mail couldn't be displayed -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Re: [freenet-dev] new stable
Newsbyte wrote: Tried it out, and thusfar...it's crap. Can you read? If so, please apply your reading skills to Matthew's announcement of the new build, particularly this part: There may be a readjustment period on the network for a while as people upgrade and the network sorts itself out. Your routing table will be reset on upgrade: the nodes will still be there but because of the algorithm change, the node will need to discover what their specialties are all over again. Ian. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Load
excuse me but seednodes looks a great point to quit the entire freenet, i start to use freenet because of it's working philosofy. my $0,02 On Thu, 2004-07-22 at 23:51, David Masover wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Toad wrote: | No, if you can do that, then you can portscan for Freenet nodes. That's | a REALLY bad idea. You need to use some sort of seednodes mechanism. Why is that a bad idea? If a government is paranoid enough, they can just put devices all over which block any crypted traffic. Some sort of way for an effective seednodes file to be chosen or built quickly, then. |Obviously clients should be able to override that, but I think that fast |node connection is feasable, if The Network (TM) was fast enough. | | | Maybe so. But we want them to be USEFUL to the network. That won't | happen if they're only up for 5 minutes. They are useful if they make it more popular. Suppose there is some lag, say, 30 seconds to a minute to get an effective seednodes.ref. On top of that, such a node probably wouldn't be able to have a terribly big cache. Then there's incentive for people to whine for permanent nodes, and it wouldn't be too long before these Public Access Internet Terminals (or whatever hype word they use now) start being preloaded with Freenet. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQQB9SHgHNmZLgCUhAQI/iBAAlmwi6Cq3M9hsrkFPMzt7R1kZm2UmVhlo FBOWVJSfNQMxNsMYNOiwdPLHBqRIoIvKJsvIbTORGu9/M283c2Voqq14RhprL14n nA518/8cAmhoBrNJuMXg5ji8IqDbX4Jn4zg40HGf5nvxSsAveGmbfVZ2T7NveKZO 6Cs87GCuxlizgstOFRKP6S5Tsvrk16skQzyevwDm9tClbS5w2mbOFnk46h1uORQB kOPLP4vggS8f6QZPAZdsTU+iKZ3FHOo9ewY2zPWj43H6vYUkejIqLzas0/IZhSkL 6xkpJKT4tg33JAmrYiPp8c/gDBUoESP6F7OrbEccsc4TYb6z/mKWO2CZa/6m5XLQ z+D1W++uypAHr3KCPCg0ejHkIHHb3ixv58vWE4Ov+g5wyrio9eKxQyVNhHmegzkg v8ttcbXsrATnoNUv2qHbIPspqpJctbgE9+d/0dcwRmHII2465GeoZNW62slJ9goO 55WNgG9kpKQpmPaYok3zTiHsd2cTHxIEbRgEKG5SK2lx9d8SHqOuCnFWKJkY7LZZ Vgk//qqzN3dbsGDB821uhjmXHeBnNy1awjwy0EufuzA28G0tiRHY/dNLI+BUtBep beHP/K8h5wBWRIrknvtFYxKQY+WK2BrXFdcjB+EYnGv/r/ySxRbJ/6yURIMD9JaG sUgy81bqMtw= =a4R+ -END PGP SIGNATURE- ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Load
I'm not sure exactly what you mean, but: In the short to medium term, central seednodes are a necessary evil. Especially as there is very little use of the Distribution Servlet/ Spread Freenet thing for more organic spreading of Freenet. Right now, Freenet traffic is relatively easy to detect. This will be fixed with Sessionv2 at some point before 1.0. In the longer term, IF routing works, it may be possible for Freenet to work with a more static mesh. Combined with steganography this would work reasonably well in hostile environments where seednodes would be dangerous. Although if the attacker has access to the whole network, they can probably do significant damage just by tracing node connections. But the point: seednodes are not necessarily the last word on all this. On Fri, Jul 23, 2004 at 10:38:33AM -0300, Lu?s Vit?rio Cargnini wrote: excuse me but seednodes looks a great point to quit the entire freenet, i start to use freenet because of it's working philosofy. my $0,02 On Thu, 2004-07-22 at 23:51, David Masover wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Toad wrote: | No, if you can do that, then you can portscan for Freenet nodes. That's | a REALLY bad idea. You need to use some sort of seednodes mechanism. Why is that a bad idea? If a government is paranoid enough, they can just put devices all over which block any crypted traffic. Some sort of way for an effective seednodes file to be chosen or built quickly, then. |Obviously clients should be able to override that, but I think that fast |node connection is feasable, if The Network (TM) was fast enough. | | | Maybe so. But we want them to be USEFUL to the network. That won't | happen if they're only up for 5 minutes. They are useful if they make it more popular. Suppose there is some lag, say, 30 seconds to a minute to get an effective seednodes.ref. On top of that, such a node probably wouldn't be able to have a terribly big cache. Then there's incentive for people to whine for permanent nodes, and it wouldn't be too long before these Public Access Internet Terminals (or whatever hype word they use now) start being preloaded with Freenet. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQQB9SHgHNmZLgCUhAQI/iBAAlmwi6Cq3M9hsrkFPMzt7R1kZm2UmVhlo FBOWVJSfNQMxNsMYNOiwdPLHBqRIoIvKJsvIbTORGu9/M283c2Voqq14RhprL14n nA518/8cAmhoBrNJuMXg5ji8IqDbX4Jn4zg40HGf5nvxSsAveGmbfVZ2T7NveKZO 6Cs87GCuxlizgstOFRKP6S5Tsvrk16skQzyevwDm9tClbS5w2mbOFnk46h1uORQB kOPLP4vggS8f6QZPAZdsTU+iKZ3FHOo9ewY2zPWj43H6vYUkejIqLzas0/IZhSkL 6xkpJKT4tg33JAmrYiPp8c/gDBUoESP6F7OrbEccsc4TYb6z/mKWO2CZa/6m5XLQ z+D1W++uypAHr3KCPCg0ejHkIHHb3ixv58vWE4Ov+g5wyrio9eKxQyVNhHmegzkg v8ttcbXsrATnoNUv2qHbIPspqpJctbgE9+d/0dcwRmHII2465GeoZNW62slJ9goO 55WNgG9kpKQpmPaYok3zTiHsd2cTHxIEbRgEKG5SK2lx9d8SHqOuCnFWKJkY7LZZ Vgk//qqzN3dbsGDB821uhjmXHeBnNy1awjwy0EufuzA28G0tiRHY/dNLI+BUtBep beHP/K8h5wBWRIrknvtFYxKQY+WK2BrXFdcjB+EYnGv/r/ySxRbJ/6yURIMD9JaG sUgy81bqMtw= =a4R+ -END PGP SIGNATURE- ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Prompts
Are you sure you have configured Freenet correctly? With the sure in there, is this not guaranteed to have the answer, Duh? ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Re: error while opening freesites
On Thu, 22 Jul 2004 17:16:10 +0200, Zenon Panoussis wrote: M. Seredszun wrote: Couldn't retrieve key: [EMAIL PROTECTED]/BPC/3//* Hops To Live: *15* Error: *Route Not Found* Can you help me Pls ? Keep trying. It's out here, I experience the same: Very many Freesites do not work initially but works when retried for several days. My node has been running since 5. April with a datastore of 66 GB with a version of Freenet and seednodes.ref never more that 1 week old. So far the storage has not been filled and I still have 6 GB of free storage. This leads me to believe, that storage in Freenet is not a problem - wheres as connectivity is. If data was inserted more redundantly then I would assume that I would not have to retry as much as I do today. So I would like to propose that every insert is inserted twice: Once as it is today and once with the key reversed. E.g: http://localhost:/SSK%40rBjVda8pC-Kq04jUurIAb8IzAGcPAgM/TFE should also be inserted as: http://localhost:/SSK%40MgAPcGAzI8bAIruUj40qK-Cp8adVjBr/TFE The reverse could also just be a hashing function. The main thing should be that the new chain of nodes that will be inserted on should not be the same as the current. /Ole ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Traffic analysis vulnerability; Unstable 60168
Unstable 60168 is now in CVS. The snapshots are updating. Stable 5086 will be released shortly. If you are running unstable it is strongly advised to upgrade as this build fixes a major vulnerability of Freenet to passive traffic analysis, relating to packet sizes. It will be a little wasteful of bandwidth, but it should work. We will improve on the bandwidth issues soon, but we needed an immediate fix to the vulnerability. I would remind all listening again that we do not guarantee that Freenet, certainly not Freenet prior to 1.0, is safe against any particular level of threat. You must balance the risks in using Freenet to access sensitive information against the cost of not using it. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] NPEs and other exceptions with 5085
Java HotSpot(TM) Client VM (build 1.4.2_03-b02, mixed mode) on Linux
2.6.7, Athlon XP. The IOExceptions are during startup, the others
when the node is running. There is also a typo in MuxConnectionHandler.java:
'utbound' rather than 'outbound'.
23.07.2004 17:40:34 (freenet.node.rt.NGRoutingTable, main, ERROR): Caught
java.io.IOException: Value out of range: 450.0 deserializing a NodeEstimator for
DataObjectRoutingMemory:tcp/x.x.x.x:x, sessions=1, presentations=3, ID=DSA(
),
version=Fred,0.5,STABLE-1.50,5085:
java.io.IOException: Value out of range: 450.0
at
freenet.node.rt.BootstrappingDecayingRunningAverage.init(BootstrappingDecayingRunningAverage.java:163)
at
freenet.node.rt.BootstrappingDecayingRunningAverageFactory.create(BootstrappingDecayingRunningAverageFactory.java:36)
at
freenet.node.rt.SlidingBucketsKeyspaceEstimator.init(SlidingBucketsKeyspaceEstimator.java:158)
at
freenet.node.rt.SlidingBucketsKeyspaceEstimatorFactory.createTime(SlidingBucketsKeyspaceEstimatorFactory.java:82)
at freenet.node.rt.StandardNodeEstimator.init(StandardNodeEstimator.java:563)
at
freenet.node.rt.StandardNodeEstimatorFactory.create(StandardNodeEstimatorFactory.java:95)
at freenet.node.rt.NGRoutingTable.loadEstimators(NGRoutingTable.java:370)
at freenet.node.rt.NGRoutingTable.init(NGRoutingTable.java:187)
at freenet.node.Main.main(Main.java:858)
23.07.2004 17:43:04 (freenet.node.Node, YThread-105, ERROR): Error while receiving
message freenet.Message: DataRequest @[EMAIL PROTECTED]
MuxConnectionHandler[conn=[tcp/connection: x.x.x.x:xlocal,[EMAIL PROTECTED], [EMAIL
PROTECTED], [EMAIL PROTECTED], identity=[DSA(
)], sock=[Socket[addr=/x.x.x.x,port=x,localport=x]],
chan=[java.nio.channels.SocketChannel[connected local=/x.x.x.x:x remote=/x.x.x.x:x]],
peer=[Peer [DSA( ) @ x.x.x.x:x
(1/3)]], utbound=[false]] @ d3e7e8e10e39862c in state [EMAIL PROTECTED] @
d3e7e8e10e39862c: java.lang.NullPointerException
java.lang.NullPointerException
at java.math.BigInteger.toString(BigInteger.java:2583)
at java.math.BigInteger.toString(BigInteger.java:2613)
at java.math.BigDecimal.toString(BigDecimal.java:931)
at java.math.BigDecimal.doubleValue(BigDecimal.java:1033)
at
freenet.node.rt.SlidingBucketsKeyspaceEstimator.interpolate(SlidingBucketsKeyspaceEstimator.java:517)
at
freenet.node.rt.SlidingBucketsKeyspaceEstimator.guess(SlidingBucketsKeyspaceEstimator.java:490)
at
freenet.node.rt.SlidingBucketsKeyspaceEstimator.guessTime(SlidingBucketsKeyspaceEstimator.java:371)
at
freenet.node.rt.StandardNodeEstimator.longEstimate(StandardNodeEstimator.java:861)
at freenet.node.rt.NodeEstimator.longEstimate(NodeEstimator.java:126)
at freenet.node.rt.NGRoutingTable.route(NGRoutingTable.java:661)
at freenet.node.rt.FilterRoutingTable.route(FilterRoutingTable.java:73)
at
freenet.node.states.request.Pending.receivedRequestInitiator(Pending.java:419)
at
freenet.node.states.request.DataPending.receivedMessage(DataPending.java:109)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at freenet.node.State.received(State.java:143)
at freenet.node.states.FNP.NewDataRequest.received(NewDataRequest.java:52)
at freenet.node.StateChain.received(StateChain.java:177)
at freenet.node.StateChain.received(StateChain.java:61)
at
freenet.node.StateChainManagingMessageHandler$ChainContainer.run(StateChainManagingMessageHandler.java:332)
at
freenet.node.StateChainManagingMessageHandler$ChainContainer.received(StateChainManagingMessageHandler.java:285)
at
freenet.node.StateChainManagingMessageHandler$ChainContainer.access$100(StateChainManagingMessageHandler.java:204)
at
freenet.node.StateChainManagingMessageHandler.handle(StateChainManagingMessageHandler.java:96)
at freenet.Ticker$Event.run(Ticker.java:323)
at freenet.thread.YThreadFactory$YThread.run(YThreadFactory.java:285)
23.07.2004 17:43:32 (freenet.node.Node, YThread-115, ERROR): Error while receiving
message freenet.Message: DataRequest @[EMAIL PROTECTED]
MuxConnectionHandler[conn=[tcp/connection: x.x.x.x:xlocal,[EMAIL PROTECTED], [EMAIL
PROTECTED], [EMAIL PROTECTED], identity=[DSA(
)], sock=[Socket[addr=/x.x.x.x,port=x,localport=x]],
chan=[java.nio.channels.SocketChannel[connected local=/x.x.x.x:x remote=/x.x.x.x:x]],
peer=[Peer [DSA( ) @ x.x.x.x:x
(1/3)]],
RE: [freenet-support] NPEs and other exceptions with 5085
There is also a typo in MuxConnectionHandler.java: 'utbound' rather than 'outbound'. Fixed now :) /N ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
[freenet-support] Stable build 5086 and major vulnerability fix
Stable build 5086 is now available. The snapshots have been updated. Please upgrade ASAP (if you are running the stable branch, which most Freenet users are). This build fixes a fairly major vulnerability to passive traffic analysis whereby an attacker could determine (on uncongested links) the types of messages being transferred, and perhaps the MRI, and with help from a node from within the network, he could perhaps trace a message chain's path across much of the network (with a lot of luck), and perhaps find compromizing information. This is the initial fix and it may be somewhat wasteful of bandwidth. We will develop better fixes in the near future, but it is at least backwards compatible: You should not need to reseed. How to update: On POSIX-like systems such as Linux and MacOS/X (or Darwin): ./stop-freenet.sh ./update.sh ./start-freenet.sh On Windows, you can use the update option on the start menu. On any platform, you can stop the node, download http://freenetproject.org/snapshots/freenet-latest.jar over your existing freenet.jar, and then start the node up again. The next build, 5087, will probably contain a significant CPU usage improvement by means of using native code to speed up some of the heaviest crypto and routing operations. That code is not quite ready yet; look for a release later on Saturday, or perhaps Monday. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. signature.asc Description: Digital signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Stable build 5086 and major vulnerability fix
Just went through the update the the web interface and log still say im running 5085. On Sat, Jul 24, 2004 at 12:48:53AM +0100, Toad wrote: Stable build 5086 is now available. The snapshots have been updated. Please upgrade ASAP (if you are running the stable branch, which most Freenet users are). This build fixes a fairly major vulnerability to passive traffic analysis whereby an attacker could determine (on uncongested links) the types of messages being transferred, and perhaps the MRI, and with help from a node from within the network, he could perhaps trace a message chain's path across much of the network (with a lot of luck), and perhaps find compromizing information. This is the initial fix and it may be somewhat wasteful of bandwidth. We will develop better fixes in the near future, but it is at least backwards compatible: You should not need to reseed. How to update: On POSIX-like systems such as Linux and MacOS/X (or Darwin): ./stop-freenet.sh ./update.sh ./start-freenet.sh On Windows, you can use the update option on the start menu. On any platform, you can stop the node, download http://freenetproject.org/snapshots/freenet-latest.jar over your existing freenet.jar, and then start the node up again. The next build, 5087, will probably contain a significant CPU usage improvement by means of using native code to speed up some of the heaviest crypto and routing operations. That code is not quite ready yet; look for a release later on Saturday, or perhaps Monday. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED] pgp3r2m3KkRZI.pgp Description: PGP signature ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
Re: [freenet-support] Weird Error
I've found that Freenet is a great tool for stress testing my system. You might want to run memtest on your box to see if you have a bad stick of memory. http://www.memtest.org/ http://www.memtest86.com/ Shoey Fighter wrote: Hello. I have recently installed Slackware 10.0 (java 1.4.2) and the latest stable build of Freenet. It worked seemingly fine for a few days, but then after letting it go by itself for a while I noticed my router wasn't showing much activity. I logged in via SSH, only to find that the service was no longer going. Confused, I started it again, and this time left the console window open to see if anything would be dumped. Eventually, the following message was dumped. (The only settings I changed in my configuration are allowedhosts=all computers on my network, maxconnections=150, ipaddress=mine, logfile=error, datastoresize=5000M). Now it takes about half of an hour (or less) for this error to come up. Any suggestions would be greatly appreciated. I can also include my configuration or any other info you might need. Thanks, ShoeyFighter Message: == Unexpected Signal : 11 occurred at PC=0x4031DF3A Function=(null)+0x4031DF3A Library=/usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm.so NOTE: We are unable to locate the function name symbol for the error just occurred. Please refer to release documentation for possible reason and solutions. Current Java thread: at java.lang.Object.wait(Native Method) - waiting on 0x45e88ee8 (a java.lang.Thread) at java.lang.Thread.join(Thread.java:1001) - locked 0x45e88ee8 (a java.lang.Thread) at java.lang.Thread.join(Thread.java:1054) at freenet.Core.join(Core.java:539) at freenet.node.Main.main(Main.java:1016) Dynamic libraries: 08048000-0804e000 r-xp 03:02 33051 /usr/lib/j2sdk1.4.2_04/bin/java 0804e000-0804f000 rw-p 5000 03:02 33051 /usr/lib/j2sdk1.4.2_04/bin/java 4000-40014000 r-xp 03:02 12031 /lib/ld-2.3.2.so 40014000-40015000 rw-p 00013000 03:02 12031 /lib/ld-2.3.2.so 40016000-4001e000 r-xp 03:02 33532 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/native_threads /libhpi.so 4001e000-4001f000 rw-p 7000 03:02 33532 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/native_threads /libhpi.so 4001f000-40029000 r-xp 03:02 12071 /lib/libnss_compat-2.3.2.so 40029000-4002a000 rw-p 9000 03:02 12071 /lib/libnss_compat-2.3.2.so 4002c000-4003a000 r-xp 03:02 12078 /lib/libpthread-0.10.so 4003a000-4003b000 rw-p e000 03:02 12078 /lib/libpthread-0.10.so 4007d000-4007f000 r-xp 03:02 12067 /lib/libdl-2.3.2.so 4007f000-4008 rw-p 1000 03:02 12067 /lib/libdl-2.3.2.so 4008-401a8000 r-xp 03:02 12065 /lib/libc-2.3.2.so 401a8000-401ac000 rw-p 00128000 03:02 12065 /lib/libc-2.3.2.so 401b-405ab000 r-xp 03:02 33536 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm. so 405ab000-405c6000 rw-p 003fa000 03:02 33536 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/client/libjvm. so 405d9000-405eb000 r-xp 03:02 12070 /lib/libnsl-2.3.2.so 405eb000-405ec000 rw-p 00011000 03:02 12070 /lib/libnsl-2.3.2.so 405ee000-4060f000 r-xp 03:02 12068 /lib/libm-2.3.2.so 4060f000-4061 rw-p 0002 03:02 12068 /lib/libm-2.3.2.so 4061-40614000 rw-s 03:02 191373 /tmp/hsperfdata_root/1286 40614000-40624000 r-xp 03:02 33525 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libverify.so 40624000-40626000 rw-p f000 03:02 33525 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libverify.so 40626000-40646000 r-xp 03:02 33540 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libjava.so 40646000-40648000 rw-p 0001f000 03:02 33540 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libjava.so 40648000-4065c000 r-xp 03:02 33530 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libzip.so 4065c000-4065f000 rw-p 00013000 03:02 33530 /usr/lib/j2sdk1.4.2_04/jre/lib/i386/libzip.so 4065f000-41fff000 r--s 03:02 33646 /usr/lib/j2sdk1.4.2_04/jre/lib/rt.jar 42049000-4205f000 r--s 03:02 33605 /usr/lib/j2sdk1.4.2_04/jre/lib/sunrsasign.jar 4205f000-4213a000 r--s 03:02 33582 /usr/lib/j2sdk1.4.2_04/jre/lib/jsse.jar 4213a000-4214b000 r--s 03:02 33652 /usr/lib/j2sdk1.4.2_04/jre/lib/jce.jar 4214b000-426a4000 r--s 03:02 33644 /usr/lib/j2sdk1.4.2_04/jre/lib/charsets.jar 4474c000-4474f000 r--s 03:02 33516 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/dnsns.jar 5080e000-5083a000 r--p 03:02 62976 /usr/lib/locale/en_US/LC_CTYPE 5083a000-50856000 r--s 03:02 33517 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/sunjce_provider .jar 50856000-50863000 r--s 03:02 33518 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/ldapsec.jar 50863000-5091f000 r--s 03:02 33519 /usr/lib/j2sdk1.4.2_04/jre/lib/ext/localedata.jar
[freenet-support] Re: Stable build 5086 and major vulnerability fix
Toad [EMAIL PROTECTED] writes: Stable build 5086 is now available. The snapshots have been updated. I've still been getting 5085 for the last 3 hours using the update option on the start menu under Windows. ___ Support mailing list [EMAIL PROTECTED] http://news.gmane.org/gmane.network.freenet.support Unsubscribe at http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/support Or mailto:[EMAIL PROTECTED]
