Modify

Opened 4 years ago

Closed 3 years ago

#16886 closed task (wontfix)

Please Release AA 12.09.1 ASAP

Reported by: anonymous Owned by: developers
Priority: highest Milestone: Attitude Adjustment 12.09.1
Component: base system Version: Attitude Adjustment 12.09
Keywords: Cc:

Description

to developer: Why not releasing AA 12.09.1 with latest security fix? So other users who do not have knowledge, resource, and/or time to compile AA can also have security benefits. especially for those who use openvpn on the router

Attachments (0)

Change History (20)

comment:1 follow-up: Changed 4 years ago by anonymous

Compile self, use precompiled images, buy other router.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 4 years ago by anonymous

Replying to anonymous:

Compile self, use precompiled images, buy other router.

Compile self: as said "other users who do not have knowledge, resource and/or time" .. i think this is valid
use precompiled images: which one? the old images which didn't include security fixes?
buy other router: and then what?

I think this is a valid and not a big request on the openwrt devs. Openwrt would benefit if it was a little bit more "consumer"-userfriendly --> more users --> more donations --> more publicity --> more developer resources.

The usual answer: "Use trunk" is not quite satisfying. trunk is very often unstable and this is for "normal" users unsatisfying.

just another comment who is

another user (who is also software developer)

comment:3 follow-up: Changed 4 years ago by TCr82

I also vote for it - using trunk snapshots has also one big problem:

when you want to install later any package (specially kernel modules) it can happen, that they dont match (because snapshot are overwritten and so the old packages are not available) - so you need to update the whole system.

comment:4 in reply to: ↑ 3 ; follow-up: Changed 4 years ago by mreeve

Replying to TCr82:

I also vote for it - using trunk snapshots has also one big problem:

when you want to install later any package (specially kernel modules) it can happen, that they dont match (because snapshot are overwritten and so the old packages are not available) - so you need to update the whole system.

Solution: The Image Builder / Image Generator archive holds all the packages compiled against that kernel, libraries, etc. Download it, unarchive it, put it on a web server somewhere your router can access, and update your opkg.conf accordingly.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 4 years ago by anonymous

Replying to mreeve:

Replying to TCr82:

I also vote for it - using trunk snapshots has also one big problem:

when you want to install later any package (specially kernel modules) it can happen, that they dont match (because snapshot are overwritten and so the old packages are not available) - so you need to update the whole system.

Solution: The Image Builder / Image Generator archive holds all the packages compiled against that kernel, libraries, etc. Download it, unarchive it, put it on a web server somewhere your router can access, and update your opkg.conf accordingly.

Also not very userfriendly and easy.

comment:6 in reply to: ↑ 2 Changed 4 years ago by anonymous

Replying to anonymous:

Replying to anonymous:

Compile self, use precompiled images, buy other router.

Compile self: as said "other users who do not have knowledge, resource and/or time" .. i think this is valid
use precompiled images: which one? the old images which didn't include security fixes?
buy other router: and then what?

I think this is a valid and not a big request on the openwrt devs. Openwrt would benefit if it was a little bit more "consumer"-userfriendly --> more users --> more donations --> more publicity --> more developer resources.

The usual answer: "Use trunk" is not quite satisfying. trunk is very often unstable and this is for "normal" users unsatisfying.

just another comment who is

another user (who is also software developer)

Not valid at all. Everyone can compile, there are several guides where you just have copy&paste, have no "exclusive" knowledge at all.

Aehm... ?? ...

http://downloads.openwrt.org/snapshots/trunk/
http://buildbot.openwrt.org:8010/

I am using trunk now over 1.2 years and update my 4 WNDR3800 every 14 days (3 of them are remote), so far for the unstable argumentation =)

comment:7 follow-up: Changed 4 years ago by anonymous

Oh and btw, all the "... and I am a software developer" and "... but I cant compile / dont want to", makes me laugh, sorry.

comment:8 follow-up: Changed 4 years ago by anonymous

question: Why do you update your 4 WNDR3800 every 14 days? Never got a problem with old configs? Missing packages? New packages? Replaced packages?
And yeah ... this makes me laugh.
A system which lost it's connection every 14 days. Yes ... very stable.
I don't say its not possible to compile openwrt. But for a "User" it should just work.
For the "users" there is the stable branch. But for now without security fixes.

comment:9 in reply to: ↑ 7 Changed 4 years ago by anonymous

Replying to anonymous:

Oh and btw, all the "... and I am a software developer" and "... but I cant compile / dont want to", makes me laugh, sorry.

yeah: i said i am a software developer. i never said i cant compile /dont want to. Learn to read, learn to think and only then maybe try to speak.

comment:10 in reply to: ↑ 5 ; follow-up: Changed 4 years ago by mreeve

Replying to anonymous:

Replying to mreeve:

Replying to TCr82:

I also vote for it - using trunk snapshots has also one big problem:

when you want to install later any package (specially kernel modules) it can happen, that they dont match (because snapshot are overwritten and so the old packages are not available) - so you need to update the whole system.

Solution: The Image Builder / Image Generator archive holds all the packages compiled against that kernel, libraries, etc. Download it, unarchive it, put it on a web server somewhere your router can access, and update your opkg.conf accordingly.

Also not very userfriendly and easy.

Yes it is. The usual Windows archive tools like WinZip, 7-zip, rar, etc can handle it. There are point-and-click web server solutions, and you don't need to preserve *nix file ownership, permissions, etc. It can be done in 10 minutes.

Sure, it's not handed to you on a silver platter, but it is at least an order of magnitude easier than preparing a linux installation, checking out the buildroot, choosing your platform, and waiting for an hour for it to compile. (Which is actually *much* easier than it sounds at first. It's not like trying to compile DD-WRT.)

comment:11 in reply to: ↑ 10 Changed 4 years ago by anonymous

Replying to mreeve:

Replying to anonymous:

Replying to mreeve:

Replying to TCr82:

I also vote for it - using trunk snapshots has also one big problem:

when you want to install later any package (specially kernel modules) it can happen, that they dont match (because snapshot are overwritten and so the old packages are not available) - so you need to update the whole system.

Solution: The Image Builder / Image Generator archive holds all the packages compiled against that kernel, libraries, etc. Download it, unarchive it, put it on a web server somewhere your router can access, and update your opkg.conf accordingly.

Also not very userfriendly and easy.

Yes it is. The usual Windows archive tools like WinZip, 7-zip, rar, etc can handle it. There are point-and-click web server solutions, and you don't need to preserve *nix file ownership, permissions, etc. It can be done in 10 minutes.

Sure, it's not handed to you on a silver platter, but it is at least an order of magnitude easier than preparing a linux installation, checking out the buildroot, choosing your platform, and waiting for an hour for it to compile. (Which is actually *much* easier than it sounds at first. It's not like trying to compile DD-WRT.)

waiting for an hour for it to compile? not everyone has resource like you. I only have atom netbook, very slow internet connection, old 150n router

comment:13 Changed 4 years ago by anonymous

+1!!!

Delicious to mention that some other OpenWRT-related projects based their work on this branch for several months now.

..so plz release AA 12.09.1 it officially... !

comment:14 in reply to: ↑ 8 Changed 4 years ago by anonymous

Replying to anonymous:

question: Why do you update your 4 WNDR3800 every 14 days? Never got a problem with old configs? Missing packages? New packages? Replaced packages?
And yeah ... this makes me laugh.
A system which lost it's connection every 14 days. Yes ... very stable.
I don't say its not possible to compile openwrt. But for a "User" it should just work.
For the "users" there is the stable branch. But for now without security fixes.

no? LOL ... (looking at answer) lol again

comment:15 in reply to: ↑ 12 Changed 4 years ago by anonymous

Replying to anonymous:

AA r41182:
without Luci => http://dl.eko.one.pl/attitude_adjustment/ar71xx/package --> not all packages available
with Luci => http://dl.eko.one.pl/luci/ar71xx/ --> not all router available

comment:16 Changed 4 years ago by anonymous

Refer to #16871 dropbear also has multiple vulnerabilities. for remote tunneling purpose.

comment:17 Changed 4 years ago by anonymous

--bump--


Need developer response

comment:18 Changed 4 years ago by anonymous

Good idea to release 12.09.1 There are many fixes in AA Git (Wi-Fi issuses are solved on Atheros-based routers etc.). Compiling source to get fixed version is OK for people, who know OpenWRT a bit, but it makes crazy new users. If AA 12.09.1 is not ready yet, why not release some updated images with current fixes?

comment:19 Changed 4 years ago by anonymous

+1 for release

comment:20 Changed 3 years ago by florian

  • Resolution set to wontfix
  • Status changed from new to closed

There is an on-going 15.05 release. 12.09 is very old and should not receive any more changes at this point, please migrate to the latest and greatest.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.